<< Weekly Status Report, W13/2010 | The roads I take... | 47 >>

Weekly Status Report, W14/2010

Here's a summary of SeaMonkey/Mozilla-related work I've done in week 14/2010 (April 5 - 11, 2010):

Build Infrastructure:
Partial updates for nightlies could be actually made working after fixing the regression I introduced on first try. For any 1-day update jump on trunk nightlies of any locale, you should now get partials via the automated update service, only larger jumps need to go through complete updates now.
In all that work, I also updated the community update server to current AUS code so that our matches all the features of the "official" one again.
Once again, I also upgraded our buildbot master to current buildbotcustom code to make sure everything continues to work smoothly there.
Not enough with that, I also turned on test packaging for optimized "dep" builds on trunk so it's easier to download and run the tests yourself, even without building on your own machine.
Once again, I also did some build system reviews, and discussed a few test failures in bugs.
As a fallout from the update discussions, I filed a bug on updating our AUS URL. And before I got to ranting more that it's not easy nowadays to keep our build machine configs on par with the Firefox ones, I filed a bug for making it easier again.
Bug Triage:
I already posted last week on possible triaging targets, but this week I did take another look of what we could do to deal with bugs more easily and in the end proposed expiring bugs that had been mass-unconfirmed 10 months ago and had no comments since then. That step would make it easier for our small community to concentrate on bugs that had some activity since our project has been started.
There also will be a Mozilla bugday on SeaMonkey "General" bugs, which should be checked and probably moved to a more appropriate component.
Internal Help Content:
As the whole interface change had been introduced by me, I volunteered on this week's SeaMonkey meeting to update help for places history and did that work later in the week, wondering how little work it actually required.
While I was on the topic, I realized I also should tend to a related trunk-only help change.
Places:
Some side discussion came up when it was discovered that some related part that wasn't really needed there but which I included in my making icons work WIP patch was actually useful elsewhere - and possibly rather now than post-places-bookmarks. I urged people to decouple issues as far as possible, and if we really need this now, implement it in a separate bug.
On the main places bookmarks patchset, there's not much to tell, other than the recent try builds are being reported to work nicely. More testing wanted!
Meanwhile, I filed bugs on getting some tests in place, updating help and UI prefs updates, which all can be done after the core of the work itself.
Various Discussions:
Build system reviews, test failures, bugday, Google Summer of Code, tabbrowser APIs, Firefox tabs-on-top experiment, SeaMonkey 2.1 progress, etc.

I'm continuing and intensifying my thinking about how we can get more people to help the SeaMonkey project. We desperately need help in marketing, support, design and bug triage areas - which all are not tied to very in-deep code knowledge but even easy to work on without any programming knowledge. If you can help us out there, please contact us - and if you know someone who can help us, please spread the word!

Beitrag geschrieben von KaiRo und gepostet am 12. April 2010 20:48 | Tags: L10n, Mozilla, SeaMonkey, Status | 3 Kommentare | TrackBack

Kommentare

Autor	Beitrag
KaiRo Webmaster	Jota.Ce: A whole lot of our code is in JavaScript and interacting with XUL markup, which is both easy to understand - and when you know VB and Pascal, that means you know basic programming structures, everything else is just a bit of syntax learning. Misak for example had not been doing any programming for years and then he came around and made session restore work in SeaMonkey, so it can't be that hard after all. As for IDE/RAD, I'm not sure what's available, I'm more the type who likes to be able to throw any editor at things and often avoid actual compiling (though I nowadays tend to use "make" and our build environment even for putting simple JS/XUL files into their correct places). Oh, and of course, we're all around on IRC in #seamonkey a lot and happy to help! 16.04.2010 18:47
KaiRo Webmaster	For the crashes, they get recorded on crash-stats.mozilla.com in any case, so nothing's lost. For all of those crashes and hangs, best is of course to have a bug report on file, ideally, with a crash ID from about:crashes output. 17.04.2010 17:21
KaiRo Webmaster	Federico: If you can, come into #seamonkey on irc.mozilla.org and/or post in the mozilla.dev.apps.seamonkey list/group about this, I'm sure that there are people around who can find you some easy or thing to look into and get acquainted with. I'm only project coordinator and not too deeply into code, those people that are probably know things off the top of their heads where you could help! 18.04.2010 14:56

Autor

Beitrag

KaiRo

Webmaster

Jota.Ce:

A whole lot of our code is in JavaScript and interacting with XUL markup, which is both easy to understand - and when you know VB and Pascal, that means you know basic programming structures, everything else is just a bit of syntax learning.

Misak for example had not been doing any programming for years and then he came around and made session restore work in SeaMonkey, so it can't be that hard after all.

As for IDE/RAD, I'm not sure what's available, I'm more the type who likes to be able to throw any editor at things and often avoid actual compiling (though I nowadays tend to use "make" and our build environment even for putting simple JS/XUL files into their correct places).

Oh, and of course, we're all around on IRC in #seamonkey a lot and happy to help!

16.04.2010 18:47

KaiRo

Webmaster

For the crashes, they get recorded on crash-stats.mozilla.com in any case, so nothing's lost. For all of those crashes and hangs, best is of course to have a bug report on file, ideally, with a crash ID from about:crashes output.

17.04.2010 17:21

KaiRo

Webmaster

Federico:

If you can, come into #seamonkey on irc.mozilla.org and/or post in the mozilla.dev.apps.seamonkey list/group about this, I'm sure that there are people around who can find you some easy or thing to look into and get acquainted with. I'm only project coordinator and not too deeply into code, those people that are probably know things off the top of their heads where you could help!

18.04.2010 14:56

Kommentar hinzufügen