WIP: Draft: Improve release management #347
No reviewers
Labels
No labels
Security
TeX
board
done
board
ready
board
todo
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
source::aleksolotl
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
aleksis/AlekSIS!347
Loading…
Reference in a new issue
No description provided.
Delete branch "improve-release-management"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Related: https://edugit.org/AlekSIS/official/AlekSIS-Core/-/merge_requests/1447
assigned to @nik
What do we need this Dockerfile for now?
It's used as base for the
docker-compose.ymland as example for building own Dockerfiles with a custom set of apps.added 2 commits
4c856cf2- Add documentation on creating releasesa9167539- [CI] Fix pip install for pages-distCompare with previous version
added 1 commit
a028c6d8- [Docs] Drop references to standard distributionCompare with previous version
@nik Please review again (especially RELEASE_MANAGEMENT.md)
This change suggests that the combined handbook now does not make a lot sense anymore… which makes me wonder how we compose a handbook now that we don't know what to put in it.
We should postpone the decision to discontinue the standard distribution until we know how we build a concise artifact now.
Probably: In general, bug fixes should be merged into master first and then get cherry-picked in a release branch for patch releases.
Pull request closed