Here is something that got me thinking recently: should we use the same workflow with regards to marking bugs as fixed for l10n bugs that we use for development bugs? Let me try to explain.
For development, the process takes place simultaneously on several branches. For example right now, we work on trunk (mozilla-central, Firefox.next), 1.9.1 [...]
Great news! Another 3 locales on the 3.0.x branch have just moved out of beta as of 3.0.9 release. This is a major milestone for these locales, their localizers, and, of course, our users who now can enjoy the polish and top quality of the final releases in their native language.
Добре дошли, хора!
Planvenguts [...]
46,8% as of today. Celebrating with Aviary.pl folks in Cracow. Legendary!
This race is only about to start :)
I’m happy to write this: in the upcoming Firefox 3.0.7 release (scheduled for tomorrow), four three of our beta locales will move out of the beta status!
Estonian (et)
Kannada (kn)
Telugu (te)
Congratulations to the localization teams that made it possible!
Seth already did two great posts about our process: So what does “getting new languages ready [...]
As you probably know, minor releases of Firefox, denoted by the third digit in the version number (or fourth in case of 2.0 releases), are intended as security and stability updates. The idea here is that there shouldn’t be any significant changes to the user interface or browser behavior between, say, version 3.0.6 and 3.0.7. [...]
© Staś Małolepszy. Powered by WordPress, theme based on the DePo Clean Theme.