<< Weekly Status Report, W27/2009 | The roads I take... | SeaMonkey 2.0 Beta 1 Is On Track, L10n Opt-In Wanted! >>

Weekly Status Report, W28/2009

Here's a summary of SeaMonkey/Mozilla-related work I've done in week 28/2009 (July 6 - 12, 2009):

It looks like Beta 1 might finally just fall into place nicely, even thought we are still tracking an issue with history import from 1.x builds, we now have a clue on how it could be fixed in toolkit code (mozilla-central appears to be fixed), but it might just not make the 2.0b1 build cutoff, unfortunately. We'll deal with that in this week's SeaMonkey Status Meeting and we'll re-evaluate if we can ship with that bug and just relnote it or if we need to have it fixed (we did ship Alpha 3 with this bug, apparently). For everything else, we look good for freezing Beta 1 this Tuesday and start builds for it later this week, making them available for testing. I hope you all will help to do that testing and hopefully clear the builds for an important milestone release, which will be the first time that we'll offer official localized release builds for all major platforms.

Entry written by KaiRo and posted on July 14th, 2009 02:18 | Tags: L10n, Mozilla, SeaMonkey, Status | 4 comments | TrackBack

Comments

AuthorEntry

Tony Mechelynck

from Brussels, Belgium

quote
1.9.1 vs. comm-central
Hmm, hmm, hmm... Ah, I see. (SeaMonkey doesn't show which ftp subdirectories are symlinks but command-line ftp does):
seamonkey/nightly/
   latest-comm-1.9.1
   latest-comm-central -> latest-comm-1.9.1
   latest-comm-central-trunk
   latest-trunk -> latest-comm-central
plus the same for -l10n, and also a latest-mozilla1.8 for Sm 1.1.x

"Either comm-central or trunk, but not both taken together, ultimately redirect to 1.9.1". Not very obvious.

I suppose the next step will be to add a "1.9.1 Branch" to SeMonkey on Bugzilla — or will it be enough to rename the existing "1.9.0 Branch"? Or should there be a "SeaMonkey 2.0 Branch" as distinct from "Trunk"? Now that the code is forked, I suppose bugs should be reported distinctly, since it isn't always obvious that a "new bug" is in Core (which is forked) or in SeaMonkey-specific code (which, IIUC, isn't).
2009-07-14 08:49

KaiRo

Webmaster

quote
SeaMonkey code is not branched yet, so there is no reason to add branches there.

And the FTP directories are an oversight, I should have deleted the symlinks will will do so now.
2009-07-14 13:38

Tony Mechelynck

from Brussels, Belgium

quote
Live-testing Sm 2.1a1pre
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090714 SeaMonkey/2.1a1pre - Build ID: 20090714000750

* Good point:
- Tighter packing of tabs on the tab bar (with my existing userChrome.css and about:config, about 60 tabs horizontally instead of 48. This makes a difference because I have slightly more than 50.

* Bad points:
- Frequent hangs (2 out of 2 times, after only a few minutes each time). First time, keyboard became totally unresponsive (even to Ctrl-Alt-F2 on Linux) and I had to hit the hardware Reset button. Second time was slightly less severe: SeaMonkey stopped responding but not the rest of X. This second time was after a click on a link in describecomponents.cgi at Bugzilla.
- Comes bundled with an "incompatible" ChatZilla (which only boasts support of Sm 1.0 to 2.0). I had "just" the time to report this, see https://bugzilla.mozilla.org/show_bug.cgi?id=504229

Summary:
Interesting but not yet dogfoodable. I'm going back to 2.0b1pre for the time being.
2009-07-15 04:58

KaiRo

Webmaster

quote
Our focus is on 2.0, the 2.1a1pre versions are only there so that we ensure builds compile and run based on mozilla-central code, but they got no development focus whatsoever.

I'd advise anyone to stay with 2.0 builds for regular testing for the moment.
2009-07-15 14:39

Add comment