<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Following the previous discussions around removing the possibility
for the interim releases, I have received no objections, and I have
not seen any serious concerns on either of the mailing lists.<br>
<br>
Therefore we are moving ahead with plans to only have one set of
Thunderbird releases as we move forward.<br>
<br>
The transition plan is pretty much the same with respect to
upgrading enterprise users as it would have been without a change:<br>
<ul>
<li>Around about 17th September, we'll release:</li>
<ul>
<li>TB 24 to our existing mainstream users<br>
</li>
<li>TB 17.0.9esr for the enterprise users</li>
<ul>
<li>ESR users will stay on the 17.0.x branch<br>
</li>
</ul>
</ul>
<li>Around about 29th Octobler, we'll release:</li>
<ul>
<li>TB 24.0.1</li>
<ul>
<li>This will be made available for all mainstream users<br>
</li>
</ul>
<li>TB 17.0.10esr</li>
<ul>
<li>Again, ESR users will stay on this release<br>
</li>
<li>17.0.10esr will be the last ESR17 release</li>
</ul>
</ul>
<li>Around 10th December, we'll:</li>
<ul>
<li>release TB 24.0.2</li>
<li>Provide an update route for 17.0.10esr users to 24.0.2, and
they will all be on the same update channel.</li>
</ul>
</ul>
<p>When it comes around to TB 31, there may be a decision to be made
as to when we update users from 24.0.x -> 31, but I would
expect us to provide the two-release overlap for ESR users in some
form.<br>
</p>
<p>Mark.<br>
</p>
</body>
</html>