<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Verdana">FYI --</font><br>
<div class="moz-forward-container"><br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
</th>
<td>Final Freeze for Ubuntu 13.10 (Saucy) at 2100UTC today</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Thu, 10 Oct 2013 11:09:30 -0600</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td>Adam Conrad <a class="moz-txt-link-rfc2396E" href="mailto:adconrad@ubuntu.com"><adconrad@ubuntu.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:ubuntu-devel-announce@lists.ubuntu.com">ubuntu-devel-announce@lists.ubuntu.com</a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:ubuntu-release@lists.ubuntu.com">ubuntu-release@lists.ubuntu.com</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>[ This is a shameless copy-and-paste from last year ]
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 three
hours 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 pink
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.
Some people may have noticed that we're also in the process of
spinning up a new port right now (our timing is impeccable, is
it not?), so uploads with clear and targetted FTBFS fixes for
arm64 will continue to be accepted for seeded packages until
Sunday night, and for unseeded pretty much right up to release.
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.
... Adam
--
Ubuntu-release mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ubuntu-release@lists.ubuntu.com">Ubuntu-release@lists.ubuntu.com</a>
Modify settings or unsubscribe at: <a class="moz-txt-link-freetext" href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-release">https://lists.ubuntu.com/mailman/listinfo/ubuntu-release</a>
</pre>
<br>
</div>
<br>
</body>
</html>