ffextensionguru wrote:So does this mean the Beta, Earlybird and Daily builds are now going to be numbered as 17.0.x (until we hit 24) or still keeping the old numbering scheme for the developmental releases (which would get rather confusing)?
Updated the main post and opened viewtopic.php?f=28&t=2639501 in TB General for information on how it's supposed to work.
There is also a lot of information in the tb-planning news group distributed over a couple of threads.
I don't see any official announcement, but from the initial schedule and the fact that there were no 10.0.13 ESR builds in progress so far, I'd assume that the 10.0 ESR is now EOL for good. I've posted viewtopic.php?f=28&t=2664791 to alert those users to upgrade to 17.0.3 ESR at this time.
rsx11m wrote:If you look at comm-release you will notice that the next release version is 17.0.2 and not 18.0; this is due to a decision to follow the 17 ESR branch until 24.0 with the releases. The 17.0.3 release should come entirely from comm-esr17/mozilla-esr17 with the 19.0 cycle once testing of that configuration is finalized (bug 815302).
Note that SeaMonkey will stick with the comm-release/mozilla-release repositories. As a consequence, MailNews Core bugs are no longer equally affecting Thunderbird and SeaMonkey. The SM 2.15 (rv:18.0) release branch comes off the default branch after merging from comm-beta, whereas the TB 17.0.2 release branch was cut off the default branch before merging and thus mirrors the 17.0 ESR state (the same happened on mozilla-release). This should be a one-time hack until the repos are cleanly separated.
Working fine for me, maybe you experienced just a temporary glitch. Building the repository graph is performed on the fly, thus may take a while given that the changesets in question are no longer quite current by now.
Also, just a heads-up that 24.0 is now on trunk until June 24, with an anticipated release date of September 17, 2013. This will determine the feature set for the upcoming ESR (and thus 24.0.x retail) branch, meaning that any features (and string changes) will have to make the first deadline (i.e., checked in before the next merge date) to be included in that branch.
Mark Banner posted the flowing to the tb-planning newsgroup:
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.
Therefore we are moving ahead with plans to only have one set of Thunderbird releases as we move forward.
The transition plan is pretty much the same with respect to upgrading enterprise users as it would have been without a change:
Around about 17th September, we'll release: o TB 24 to our existing mainstream users o TB 17.0.9esr for the enterprise users + ESR users will stay on the 17.0.x branch
Around about 29th Octobler, we'll release: o TB 24.0.1 + This will be made available for all mainstream users o TB 17.0.10esr + Again, ESR users will stay on this release + 17.0.10esr will be the last ESR17 release
Around 10th December, we'll: o release TB 24.0.2 o Provide an update route for 17.0.10esr users to 24.0.2, and they will all be on the same update channel.
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.
I've updated the Lightning information, they introduce a new "major" release after each 10 "minor" releases. Thus, after 2.9 (matching TB 27.0) the next Lightning version is 3.0 (matching TB 28.0). I've also added the link to MDN from viewtopic.php?f=29&t=2808077&p=13398887#p13398887 .
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.