Thunderbird/StatusMeetings/2012-07-31: Difference between revisions

← Older edit

Thunderbird/StatusMeetings/2012-07-31 (view source)

Revision as of 14:10, 1 August 2012

2,828 bytes added , 1 August 2012

→‎Roundtable Highlights

Mconley

Confirmed users, Bureaucrats and Sysops emeriti

998

edits

@@ Line 124: / Line 124: @@
 === Roundtable Highlights ===
+* There is a sense in the community that Mozilla we'll be committed to Thunderbird for the next ESR, but after that, they're on their own.
+* Jb responds: we're quite confident that the ESR program will be renewed beyond TB 24.
+** Both Firefox ESR and B2G will be carrying on with the ESR, so it's likely that TB ESR will also be perpetuated.
+** There's no reason at this point why Mozilla should stop the Thunderbird support commitment.
+** There is a high chance that we will be supporting TB for many years, but there are still a few things up in the air before we can say that with absolute certainty.
+** "For the foreseeable future" might be the right phrase for this.  There's a bit of a perception problem, because people think we're EOLing TB.
+** rkent says: TB is more important for enterprises and offices…so we can't be tied to FF's position on the Enterprise
+*** Jb: The TB team isn't in a position where we can really influence this beyond expressing a need.
+* What is the status of MailDir?
+** David Bienvenu was working on it. Last we heard, some of the tests were still failing (XPCShell when applied to maildir). He wanted to finish it off, but he needs more time. He hasn't committed to finishing it, but he's like to finish it if possible.
+* What is the obstacle to Lightning integration with the product?
+** This has been an ongoing discussion. Shipping it means that we endorse the product, and take on the responsibility of managing and maintaining it, which is kind of outside of the scope of TB. It's a significant piece of code to maintain and take ownership of. We're exploring better ways of packaging Lightning with Thunderbird ([http://www.bespokeio.com/ beSpoke], for example).
+** rkent asks: Doesn't this mean that Lightning === Thunderbird in terms of support commitment?
+*** Jb: No, not at all. We're committed to supporting users using Thunderbird. We don't make any such commitment with Lightning.
+* In Jb's original email - there's 2 releases, there's the ESR release, and some other release (based off of the ESR codebase).  How are we not going to get totally busted when switching to the NEXT ESR?  We're having a hard enough time fixing m-c breakage each 6 weeks
+** Jb / Standard8:  We'll maintain comm-central along-side the ESR releases. There's still a lot of fuzziness around Aurora and Beta, and what we're going to do there.
+*** But we WILL be keeping comm-central working. We're committed to keeping TB up to date with Gecko.
+* What is the sense of the user community in terms of the responsiveness of the TB development team?
+** Nobody is getting ignored on GetSatisfaction or Bugzilla… but we're understaffed, overworked, there are 24 hours in the day, and stuff falls off the radar sometimes. :/
+** Hopefully the paper cuts initiative will help deal with some of these.
 === Attendees ===
 __NOTOC__