Edit Info Other
Login

PrepareRelease"

Differences between revisions 22 and 32 (spanning 10 versions)
Revision 22 as of 2010-11-09 18:53:17
Size: 3365
Comment:
Revision 32 as of 2025-04-12 23:57:10
Size: 4685
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## Please edit system and help pages ONLY in the master wiki!
## For more information, please see MoinMoin:MoinDev/Translation.
Line 2: Line 4:
##master-page:Unknown-Page
##master-date:Unknown-Date
#acl -All:write Default
#format wiki
#language en
<<TableOfContents(5)>>

Line 12: Line 22:
  *  build final rpmfusion-{non,}free packages to for release in question where the release and updates repo are enabled, but development disabled; generate a new rawhide key and include it as well;   * build final rpmfusion-{non,}free packages to for release in question where the release and updates repo are enabled, but development disabled; generate a new rawhide key and include it as well;
Line 14: Line 24:
  * adjust rpmfusion-{non,}free-remix-kickstarts to use proper mirror manager urls  * Verify that every packages got signed with the proper release key. Resign packages that are not (such the one that are inherited).
Line 16: Line 26:
 * Prepare a "RPM Fusion is ready for F X" announcement mail   * Push the said packages.
Line 18: Line 28:
= When Fedora release is finished =   * Adjust the symlinks for rawhide to point to the new rpmfusion-{,non}free-release and rsync with the primary mirror.

= When RPMFusion release is finished (updated in 2025) =
Line 28: Line 40:
 * create empty updates{,-testing} repos  * create empty updates{,-testing} repos
 
 * update wiki:
 
   * Update the frontpage Wiki.
 
   * Update Configuration Wiki page.

   * Update Keys Wiki page. (Reference the new gpg keys in the wiki.)

 * Update mock-rpmfusion (the mock configurations fo rpmfusion).

 * check if rfpkg is working

 * check if mirrormanager was updated by Adrian and if mirrors are updated

 * check if [[CommonBugs | CommonBugs - RPM Fusion ]] needs updates

 * update bugzilla component version

 * Prepare a "RPM Fusion is ready for F X" announcement mail
Line 63: Line 95:
 * add taret for new release in bugzilla  * Resign early the packages in rawhide with new key.

 * add target for new release in bugzilla

= When RPMFusion branch is finished (updated in 2025) =

 * update wiki:
 
   * Update the frontpage Wiki.
 
   * Update Configuration Wiki page.

   * Update Keys Wiki page. (Reference the new gpg keys in the wiki.)

 * Update mock-rpmfusion (the mock configurations fo rpmfusion).

 * check if mirrormanager doesn't miss last stable branch and if mirrors are updated
Line 69: Line 117:
 * update wiki:

  * frontpage

  * keys

  * installation notes

 * resign development rpms
 
Line 85: Line 123:
 
----
CategoryInfrastructure

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; generate a new rawhide key and include it as well;
  • Verify that every packages got signed with the proper release key. Resign packages that are not (such the one that are inherited).
    • Push the said packages.
    • Adjust the symlinks for rawhide to point to the new rpmfusion-{,non}free-release and rsync with the primary mirror.

When RPMFusion release is finished (updated in 2025)

  • 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 -al development/X/Everything
  • create empty updates{,-testing} repos
  • update wiki:
    • Update the frontpage Wiki.
    • Update Configuration Wiki page.
    • Update Keys Wiki page. (Reference the new gpg keys in the wiki.)
  • Update mock-rpmfusion (the mock configurations fo rpmfusion).
  • check if rfpkg is working
  • check if mirrormanager was updated by Adrian and if mirrors are updated
  • check if CommonBugs - RPM Fusion needs updates

  • update bugzilla component version
  • Prepare a "RPM Fusion is ready for F X" announcement mail

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; 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

When RPMFusion branch is finished (updated in 2025)

  • update wiki:
    • Update the frontpage Wiki.
    • Update Configuration Wiki page.
    • Update Keys Wiki page. (Reference the new gpg keys in the wiki.)
  • Update mock-rpmfusion (the mock configurations fo rpmfusion).
  • check if mirrormanager doesn't miss last stable branch and if mirrors are updated

Fixme

Needs to be added to the proper places

  • recreate repoview with proper title:
    for i in */{os,SRPMS}/ ; do cd ${i}; repoview -f -s ../../source/SRPMS/ -t "RPM Fusion (Fedora - nonfree - released) 12 ($(dirname ${i}))" . ; cd - ; done
    # alternate:
    repo=free ; release=14; for i in */{os,debug,SRPMS}/ ; do cd ${i}; /usr/bin/createrepo -q -d --unique-md-filenames --changelog-limit=8 -s sha256 . ;  repoview -f -s ../../source/SRPMS/ -t "RPM Fusion (Fedora - ${repo} - released) ${release} ($(dirname ${i}))" . ; cd - ; done


CategoryInfrastructure

Infrastructure/PrepareRelease (last edited 2025-04-14 01:01:14 by Sérgio Basto)