<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
The drivers have been discussing the various mechanisms around
releasing Miramar. We're going to need to treat Miramar like the
old-style releases because we've effectively missed getting on the
central/aurora/beta/release train for Gecko 5 - if we try to do that
now, L10n would get about a week after string freeze before
localisations would have to be complete, which obviously isn't
acceptable.<br>
<br>
The good news is that we believe we can get Miramar released on the
same schedule as Gecko 5, and get the next version of Thunderbird up
and running on the release train for Gecko 6.<br>
<br>
As I've already mentioned, we're going to treat Miramar in an
old-style way of releases. So we'll be creating new clones,
releases/comm-miramar, releases/mozilla-miramar and
releases/l10n-miramar (I was thinking of using -5.0 as the shared
part of the name, but decided that would get confusing as the real
source of that is the release train repos).<br>
<br>
Now to break down what is happening by dates, note that this doesn't
cover Thunderbird.next from Gecko 6.0 - I'll be doing a separate
note covering that.<br>
<br>
First, here's a quick diagram to explain what's happening, notes on
the various periods are below.<br>
<br>
<div align="center"><img
src="cid:part1.02000901.09060306@mozilla.com" alt=""><br>
</div>
<ul>
<li>Until May 10th:</li>
<ul>
<li>comm-central and mozilla-aurora will be the main locations
for Miramar checkins</li>
<li>During this period, build & release will work on getting
comm-miramar and mozilla-miramar up and running.</li>
<ul>
<li>We may also transition builders to this set up, if we can
get automated pulls and pushes from comm-central to
comm-miramar (should be easily doable).<br>
</li>
</ul>
</ul>
<li>May 10th: String & Feature Freeze</li>
<ul>
<li>At this point comm-miramar will formally branch from
comm-central</li>
<li>comm-central and mozilla-central will become the new nightly
builds</li>
<li>comm-miramar, mozilla-miramar and l10n-aurora will be the
Miramar repos at this stage</li>
<ul>
<li>mozilla-miramar will be synced with whatever comes into
mozilla-aurora<br>
</li>
</ul>
</ul>
<li>May 17th:</li>
<ul>
<li>This is the merge of aurora to beta channel for Firefox</li>
<li>Here we change mozilla-miramar so that it is synced with
mozilla-beta</li>
<li>The l10n repositories are changed to l10n-miramar, and those
repositories get filled with the data from the l10n-aurora
repositories at the Firefox aurora -> beta channel merge
point</li>
</ul>
<li>May 17th - 7th:</li>
<ul>
<li>At this point we'll be releasing Miramar onto the beta
channel, and may do multiple releases as appropriate<br>
</li>
</ul>
<li>June 7th:</li>
<ul>
<li>Initial Deadline for L10n changes</li>
</ul>
<li>June 21st - 28th (exact date TBD):</li>
<ul>
<li>Release Miramar</li>
</ul>
</ul>
Mark<br>
</body>
</html>