Edit Info Other
Login

PrepareRelease"

Differences between revisions 7 and 9 (spanning 2 versions)
Revision 7 as of 2008-11-22 18:25:02
Size: 891
Comment:
Revision 9 as of 2008-11-26 18:45:44
Size: 1182
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:

 * Prepare a "RPM Fusion is ready for F X" announcement mail
Line 23: Line 25:

= branching =

When?
{{{
for j in free nonfree; do for i in /cvs/${j}/rpms/*/devel/*.spec,v ; do echo /usr/local/bin/mkbranchwrapper-${j} $(basename $(dirname $(dirname ${i}))) F-10; read -t 1 -s -n 1 ; done; done
}}}

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 for broken deps and broken packages and finally get them 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
  • 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

When?

for j in free nonfree; do for i in /cvs/${j}/rpms/*/devel/*.spec,v ; do echo /usr/local/bin/mkbranchwrapper-${j} $(basename $(dirname $(dirname ${i}))) F-10; read -t 1 -s -n 1 ; done; done

Infrastructure/PrepareRelease (last edited 2024-04-20 17:21:05 by Sérgio Basto)