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

Weekly Status Report, W17/2012

Here's a short summary of Mozilla-related work I've done in week 17/2012 (April 23 - 29, 2012):

Another release and uplift week is behind us, and while the release of Firefox 12 went smoothly, getting 13 to beta showed us a grave crasher (which we are happy to catch that early and not have in release, but which causes discomfort for beta testers) - and getting the new Firefox 14 for Android to Aurora is a bit delayed as well in terms of opening the flood gates for automatic updates, but we're near. Once we have it up there, and even more when we go to beta with it (way earlier than the normal 14 beta train), we'll want a lot of people testing this on their Android phones and giving us feedback. If you have such a device with an ARMv7 processor (ARMv6 support is in the works but not complete yet), I hope you'll be among those testers!

And, as usual, please send crash reports from all your installations, we look at them and try to fix the problems, esp. if multiple people are sending reports for them! ;-)

Beitrag geschrieben von KaiRo und gepostet am 30. April 2012 22:23 | Tags: L10n, Mozilla, SeaMonkey, Status | 2 Kommentare | TrackBack

Kommentare

AutorBeitrag

Norihiko Murase

aus Japan

zitieren
Request of fix of bug #665024!!
Hi,

I thank you very much for your work on SeaMonkey. I use this
software since it was "Mozilla Suite".

However, I frequently feel much ANNOYED with the following bug:
665024 – History window isn't updated when entry is deleted
https://bugzilla.mozilla.org/show_bug.cgi?id=665024
whose status has been "NEW" for 10 months.

As the comments of this bug say, this bug is present since
Version 2.2.

Is it possible to be fixed by small amount of change, or, is
the heavy modification required? which?

Thanks,
Norihiko Murase
03.05.2012 13:15

KaiRo

Webmaster

zitieren
Sorry, I'm not doing much work on SeaMonkey any more, almost no time left next to trying to reduce Firefox crashes.
06.05.2012 00:33

Kommentar hinzufügen