The release manager owns the stable branches
I think this helps the release manager because it means they don't have to worry about others pushing commits at the last minute.
This commit is contained in:
parent
c4c41007ad
commit
559c363b1e
1 changed files with 1 additions and 0 deletions
|
@ -6,6 +6,7 @@ It starts 7 working days before the release.
|
||||||
The release manager doesn't have to perform all the work but must ensure someone is assigned.
|
The release manager doesn't have to perform all the work but must ensure someone is assigned.
|
||||||
The current release manager must schedule the appointment of the next release manager.
|
The current release manager must schedule the appointment of the next release manager.
|
||||||
The new release manager should create overall issue to track the progress.
|
The new release manager should create overall issue to track the progress.
|
||||||
|
The release manager should be the only person pushing/merging commits to the x-y-stable branches.
|
||||||
|
|
||||||
## Release Manager
|
## Release Manager
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue