<< Weekly Status Report, W22/2008 | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>

Weekly Status Report, W23/2008

Here's a summary of SeaMonkey/Mozilla-related work I've done in week 23/2008 (June 2 - 8, 2008):

While I'm working on getting us to a new build structure that allows us to have SeaMonkey and Thunderbird source in a new, shared hg repository and build with mozilla-central/1.9.1, I'm getting more and more convinced that both our projects should ditch 1.9.0.x and go straight for 1.9.1 instead, leaving cvs behind for our development. There's still a bit of work to do before everything runs smoothly that way, but I think the sooner we do this the easier we can deliver a release on the new version control infrastructure - and the easier we still can get platform changes into Mozilla 1.9.1 where we come across needing those. Note though that this is completely my personal opinion, there has been no decision in either of our two projects about this.

Entry written by KaiRo and posted on June 9th, 2008 21:21 | Tags: L10n, Mozilla, SeaMonkey, Status | 2 comments | TrackBack




sure, 1.9.1
Sounds good to me (just a long-time SeaMonkey/TB/FF user).

In the Google groups discussions, I noticed a fear that SeaMonkey/Thunderbird might need a stable release off 1.9.1 before Firefox 3.x. Well, gee, at some point the Mozilla platform might actually have to step up to meet the needs of some other project besides Firefox!! Shocking, I know. </rant>
2008-06-09 23:50

Jens Hatlak

from Frankfurt, Germany

Brave New World
Interesting news. Even though I keep reading PlanetMo it seems to me the whole mozilla-central thing, especially the CVS to Mercurial switch, happened rather quietly looking from the outside. There's plenty of documentation about how Mozilla uses CVS (because it did so until now, for years) and how to use CVS to pull sources etc. but there's little information (that I know of) about the new system and the implications of the change. I especially miss someone posting an article about it. For example, is there a tool matching Bonsai CVS Checkins that also turns bug references into Bugzilla links? What is the LXR equivalent? All those CVS-dependent tools we're familiar with need to have a counterpart in the "new world". Anyway, I hope someone clears things up once a final decision is made. I think it would be a pity if one day the SM trunk action switched to hg and no-one outside the inner developers circle knew how to effectively track it.
2008-06-10 02:04

Add comment