Mitchell Baker's memo

Tony Mechelynck antoine.mechelynck at gmail.com
Tue Dec 1 12:21:42 UTC 2015


The way I read that memo, it does not necessarily mean death to either
Thunderbird or SeaMonkey, depending on how their respective developer
communities can weather the changes. It does, however, sound like a
death toll for the project of merging comm-central into
mozilla-central ( https://bugzilla.mozilla.org/show_bug.cgi?id=787208
), which concerns both Thunderbird and SeaMonkey. The latter may be
good or bad news depending on how we view it:

Advantage: one fewer change to how our apps are built, so the existing
order may continue as long as it remains feasible. For instance until
and unless it is decided to base Thunderbird on a forked Gecko — which
would entail its own can of worms, for instance about how and when to
port which security fixes. It also means no need to change procedures
(so far) for anyone generating one's own builds.

Disadvantage: it means that comm-central will (in the foreseeable near
future at least) still include a clone of mozilla-central which will
have to be brought up-to-date (as we are doing now, automatized in
client.py) before every build of Thunderbird or SeaMonkey. The lesser
repositories (the LDAP JDK, of which we use a "frozen" version IIUC,
and, at least for SeaMonkey, DOMi and ChatZilla) are also cloned into
comm-central but they pose less of a problem because they are
comparatively small, and evolve far less rapidly than mozilla-central.

It also means less and less concern over time for us volunteer
developers on the part of MoCo management and in a somewhat lesser
degree of Firefox, but that was already no secret for anyone not
totally blind in the Thunderbird and SeaMonkey developer and QA
communities.

IMHO the Thunderbird and SeaMonkey build engineers should follow any
developments with all due care, and preferably in concert. Even if
they decide not to follow the same policy (as they already did: ATM
there is a SeaMonkey release every six weeks unless some incident
makes us miss a release, but IIUC Thunderbird only has ESR releases,
meaning one major release every eight months or so), IMHO it is best
to keep posted on what the partner does.

Best regards,
Tony.

On Tue, Dec 1, 2015 at 10:30 AM, Dave Koelmeyer
<dave.koelmeyer at davekoelmeyer.co.nz> wrote:
> Hi Axel,
>
> Here we are:
>
> https://groups.google.com/forum/#!topic/mozilla.governance/kAyVlhfEcXg
>
>
> Cheers,
> Dave
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.nz
> GPG Key ID: 0x238BFF87
>
>
>
> On 01/12/15 22:25, Axel Grude wrote:
>
> Dear Dave,
>
> do you have a link to the memo? can't find it on her blog...
>
> Axel
>
> --
> Axel Grude
> Software Developer
> Thunderbird Add-ons Developer (QuickFolders, quickFilters, QuickPasswords,
> Zombie Keys, SmartTemplate4)
> AMO Editor
>
> Subject: Mitchell Baker's memo
> To: Tb-planning
> From: Dave Koelmeyer
> Sent: Tuesday, 01/12/2015 08:51:31 08:51 GMT ST +0000 [Week 48]
>
> Hey folks,
>
> Apropos of the subject line, I expect this to kick off a second wave of
> hysteria in the blogosphere about Thunderbird being "dead". I'll be
> pushing positive news and articles as per normal on the social networks,
> but some discussion about how we might prepare for this could might be a
> good idea – perhaps an official blog post from the Council's view which
> we could promulgate.
>
> Cheers,
> Dave
>
>
>
>
>
> _______________________________________________
> tb-planning mailing list
> tb-planning at mozilla.org
> https://mail.mozilla.org/listinfo/tb-planning
>
>
>
> _______________________________________________
> tb-planning mailing list
> tb-planning at mozilla.org
> https://mail.mozilla.org/listinfo/tb-planning
>



More information about the tb-planning mailing list