ReleaseEngineering/Meetings/2008-apr-21

= Fedora Release Engineering Meeting :: Monday 2000-04-21 =

Preview Release

 * PR was made available via torrents on Friday
 * Attempting to sync release trees to master mirrors so that we can offer direct (and jigdo) downloads
 * upload is mostly done--waiting for snapmirror to sync up the various RH netapps
 * after sync is complete will flip a bit and let the mirrors get it

CVS Branching

 * 36+ hours of outage for branching
 * cannot do this again--must to figure out a way to do this without an outage
 * the second batch of cvs branches is about 50% of the way through which started 11~ hours ago
 * part of the delay is the pkgdb updates--a different SCM wouldn't necessarily fix the problem

Release Candidate
1. They're real RCs, as in "we think we fixed all we're going to take, so now we're going to do the composes that, if they turn out right, are what we ship" 1. RC will not be a public release 1. Everyone can do composes leading up to RC for testing various fixes 1. Using pungi people outside of Red Hat can create their own RC using rawhide
 * not "hey that RC passed, now go compose the final"
 * lead time to get bits moved around just takes too long for it to be really worth it

Tagging SOP

 * need writeup on Release Engineering process and steps to tag packages at freeze
 * add something to http://fedoraproject.org/wiki/ReleaseEngineering/SOP/FreezingRawhide

IRC Transcript

 * 1) !html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">  2008-04-22-14:30-meeting-snapshot    2008-04-22-14:30-meeting-snapshot

Generated by irclog2html.py 2.3 by Marius Gedminas - find it at mg.pov.lt!