[Mailed to various lists; followups directed at dev-apps-thunderbird]
Our development schedule has today (Tuesday, Jan 12, at 23:59 Pacific)
marked as when we go into string & code freeze for Thunderbird 3.1
(Lanakai) Alpha 1 (see
<https://wiki.mozilla.org/Thunderbird:Thunderbird3.1> for more detail).
Sadly, I've had my attention spread out across a number of other things
over the last week, including being sick, so I haven't gotten as much
3.1-related stuff as I hoped lined up. That said, given Thunderbird's
move towards agility, I'm somewhat inclined to code freeze what we've
got, because there will be another release train (beta 1) coming along
soon enough.
That said, I don't have yet have a good enough feel for whether that's
the right thing to do. In particular:
As I understand it, we don't have a working l10n dashboard for
comm-central+1.9.2 (sipaq, Standard8 or anyone else, do you have a feel
for how much work it's likely to be for whom to make that happen?).
Given that l10n freeze is currently scheduled for a week from today
(Monday, January 18th), I assume that a somewhat likely outcome here is
that it would end up being hard (impossible?) to ship 3.1a1 in any
locales other than en-US (confirmation here would be appreciated). My
suspicion is that that wouldn't be a huge deal, given the relatively
small amount of feature work that's gone into 3.1. If people disagree,
I'd be very interested in hearing what specific negative consequences
seem likely.
Another thing that I don't have a good feel for is how tied up QA folks
are with 3.0.1 stuff. QA folks, how likely do you think you'd be to
have sufficient bandwidth to feel good about handing off 3.1a1 to build
on Tuesday, January 19th (one week from tomorrow)? Worth keeping in
mind is that metrics show that, today, we had 310 active daily users of
3.1 (not that I really know what to compare that to).
I'm not aware of any other possible reasons to slip the release, but
it's certainly possible they exist.
Thoughts?
Dan