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):

• Automated Testing:
  TUnit on the Linux tinderbox is off now, the new buildbots are happily running that instead.
  Unfortunately, we still have no clue why a few autocomplete tests fail only on the Mac unit test machine but not on the other platforms. Help would be appreciated.
• Version Control and SeaMonkey Development:
  I spent most of my time this week on trying to get a proof of concept on "option A" of Benjamin's repository options doc, actually with nice success. A bug report for tracking this is now open, app-config.mk/app-rules.mk have been introduced to help us there (thanks Benjamin!), and I filed a bug on the make-makefile issue with that, with a hacky patch for now, but Ted is looking into a better solution.
  In the end, I got SeaMonkey and Thunderbird to generate working build off that structure, a doc about how to get it to work is up on the wiki, but it still describes a few hacks (mainly the symlinks into mozilla/). We can ride on the Mozilla build system even with our repository being the parent of mozilla/ - we just need to prefix the --enable-application value with ../ and have the objdir path end in /mozilla, but we probably can hide both of those via top-level build system entry files (client.mk/configure) in our own repository once we have one. I also (locally) have a client.py that pulls all the source we need.
  All in all, there are a few things we still need to figure out, but there's a good proof-of-concept of the structure, opening the possibility to chose this option for our future. I may possibly do another post with more details in the next few days.
• SeaMonkey Status Meetings:
  This is still on my TODO list, I'd really like to get something going there.
• Various Discussions:
  Mail client cert prompts, about: privileges, OS X address book, MoFo ED Search, Thunderbird/mailnews development, mozilla-central/1.9.1, etc.

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.