First bunch
Something like 0 to 14 days before release branch cvs:
- add line for new release in CVS at {non,}free/common/branches (leave the devel entry as it is)
- create and add new mock config files to all builders; let them use rawhide (as the directories for the new release is not there yet) temporary as there are no updates repos yet
- create amnd add target files for plague-builders and restart them; then create and add target files for plague-server and restart them
- some more steps on the CVS box that only Xavier knows
- Branch in CVS:
for j in free nonfree; do for i in /cvs/${j}/rpms/*/devel/*.spec,v ; do packagename=$(basename $(dirname $(dirname ${i}))); if [[ -e /cvs/${j}/rpms/"${packagename}"/dead.package ]]; then echo "${packagename} seems to be a dead.package, but contains a spec file" >&2; else echo /usr/local/bin/mkbranchwrapper-${j} ${packagename} F-12; fi ;read -t 2 -s -n 1 ; done; done &> logadjust config files for push scripts and test the scripts; wun WhatsNew.py once with each config
Second part
When new release is out and rawhide is rolling towards the next release again:
- finally adjust the dist release in CVS at {non,}free/common/branches
- adjust dist tag and release version in mock config files of all builders
- adjust config files for new release to point to new directories instead of rawhide
- build a new release rpm that has rpmfusion-rawhide enabled and stock repos disabled
- Resign early the packages in rawhide with new key.
- add target for new release in bugzilla