|
Size: 640
Comment: page was renamed from Admins/PrepareRelease
|
Size: 2559
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| = A 10 days before estimated Fedora release = | = About 10 to 14 days before estimated Fedora release = |
| Line 6: | Line 6: |
| = When final fedora-release is built and published = | * check more aggressively for broken deps and broken packages to make sure they get fixed |
| Line 8: | Line 8: |
| * Add aliases to mirrormanager; once done build final rpmfusion-{non,}free packages to for release in question where the release and updates repo are enabled, but development disabled | = When final fedora-release got built and published = * Add aliases to mirrormanager; once done * build final rpmfusion-{non,}free packages to for release in question where the release and updates repo are enabled, but development disabled * adjust rpmfusion-{non,}free-remix-kickstarts to use proper mirror manager urls * Prepare a "RPM Fusion is ready for F X" announcement mail |
| Line 14: | Line 22: |
| * remove all -kmod- packages from the repos | * remove all packages that have broken deps |
| Line 16: | Line 24: |
| * rebuilt all kmod packages and make sure akmods packages get built | * remove all *-kmod-src.rpm packages from the repos; at the same time rebuilt all kmod packages and make sure akmods packages get built * mkdir releases/X; cp development/X/Everything * create empty updates{,-testing} repos = branching = == 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 &> log }}} * adjust config files for push scripts and test the scripts == 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 |
About 10 to 14 days before estimated Fedora release
- open freeze: tell packagers to only build packages if there is a strong reason to
- check more aggressively for broken deps and broken packages to make sure they get fixed
When final fedora-release got built and published
- Add aliases to mirrormanager; once done
- build final rpmfusion-{non,}free packages to for release in question where the release and updates repo are enabled, but development disabled
- adjust rpmfusion-{non,}free-remix-kickstarts to use proper mirror manager urls
- Prepare a "RPM Fusion is ready for F X" announcement mail
When Fedora release is finished
- remove all packages that are known to be broken
- remove all packages that have broken deps
- remove all *-kmod-src.rpm packages from the repos; at the same time rebuilt all kmod packages and make sure akmods packages get built
- mkdir releases/X; cp development/X/Everything
- create empty updates{,-testing} repos
branching
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 &> log- adjust config files for push scripts and test the scripts
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