<< APNG Throbber Bubbling Up In Nightlies | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>

Weekly Status Report, W03/2009

Here's a summary of SeaMonkey/Mozilla-related work I've done in week 03/2009 (January 12 - 18, 2009):

In this week's status meeting, we have decided to give SeaMonkey 2.0 Alpha 3 another week of development compared to the previous schedule, so that we can keep our code freeze in sync with Thunderbird. We will now take code changes for this last alpha until February 5 and hope to make builds, test them and get them out to the public soon afterwards. This won't change the schedule we have in mind for final as we only have rough dates even internally so far - and there's not much secrecy about what we have in mind: After this alpha, we're planning on only one beta before the final release so far, with about one and a half months of development/testing time between milestones, it's an easy guess where rough planning takes us. I stated previously that we target the second quarter of 2009 for the final release, I hope we really won't slip those rough schedules as far as to not make that - as you can calculate, we have some flexibility for this to still stay withing the range of that quarter.
This summer, we should have a stable toolkit-based SeaMonkey release for everyone out there! :)

Entry written by KaiRo and posted on January 19th, 2009 22:45 | Tags: L10n, Mozilla, SeaMonkey, Status | 2 comments | TrackBack



Jens Hatlak

from Frankfurt, Germany

One thing that is not clear from bug 390025 is what happened with "Use encryption when storing sensitive data". I see it got removed but there's no statement why, e.g. whether LoginManager does this by default.
2009-01-20 09:30



What happened is the latter assumption you made: Encyrption (with an empty master password) is the default in LoginManager, merely "obscuring" by encoding passwords in base64 is the option that's actually gone now.
2009-01-20 15:23

Add comment