[ Another cycle, another shameless copy and paste email... ]

For the timezone challenged, as of 2100UTC today, the archive is
officially fozen in preparation of release candidates and the
final release of Saucy Salamander in a week.  This is one hour
from the time I hit send on this email.

Uploads from here on in should fall into the following 4 bins:

1) Installer/release-critical bugs that absolutely MUST get fixed
   lest we risk shipping a broken image that turns computers mauve
   or sets them on fire:  Please contact the release team about
   these bugs and upload (well-tested) solutions ASAP.

   Last minute hardware enablement fixes, and pretty much anything
   installer related that is auditable and testable also falls in
   to this category, as our best installer testing comes in the
   next few days, historically.

   Much like last cycle, this one also had some new porting going
   on (we do enjoy our fun toys), and like last cycle, we'll gladly
   take FTBFS fixes pretty close to the wire, as long as they're
   clear and easily reviewable.

2) Non-release-critical-but-nice-to-have bugfixes:  These are
   fixes that you would absolutely feel comfortably about doing
   as an SRU but not necessarily destabilising the release process
   for.  Again, contact the release team, and we may slip some of
   these in, while asking you to defer the rest to SRUs.

3) Feature additions, massive code refactoring, user interface
   changes, non-typo string changes:  Just don't upload these, or
   ask about them.  The time for them came and went long ago.

4) Updates to non-seeded packages:  Technically, unseeded packages
   don't freeze until pretty much right before release.  While this
   is true, we may still try to talk you out of pushing some huge
   new upstream version of something, or start a library transition
   at the zero hour.  We're only a week away from opening the next
   release, a bit of patience (or prepping in a PPA, etc) might be
   a decent plan.

Here's hoping everyone gets on board with testing images, helping
to fix absolutely critical bugs, donating spare creative cycles to
the release notes, and any other way we can all contribute to yet
another great Ubuntu release.

And don't forget kids, this one's an LTS.  It's the release you'll
install for your friends, family, and work networks and then promptly
forget about for two years because it's just that awesome.  At least,
it should be.  So, if it's not, let's make sure we sort that out.

On behalf of the Ubuntu Release Team,

... Adam Conrad

Ubuntu-release mailing list
Modify settings or unsubscribe at: 

Reply via email to