[Localization] [Sugar-devel] [ANNOUNCE] 0.94 schedule update: still on track

[Chris Leonard]

Just to emphasize that a "string freeze" is the signal for localizers
to really shift into high gear and complete the current Glucose and
Fructose string sets and for language admins to review and commit
those PO files.

If watching PO file commits roll in is your idea of a good time (I
know it gives me a thrill), please feel free to keep an eye on our new
piece of tracking infrastructure which catches all Sugar Labs and
eToys PO file commits.  There is a slim chance that one or two Honey
actviities still hosted at dev.laptop.org might not be reported (maybe
Watch&Listen), but the overwhelming majority of Pootle commits to
Sugar projects will now be reported and archived on the list below:

http://lists.sugarlabs.org/archive/pootle-commits/\

Localizers, start your engines.  Developers, put on your localizer hat
for a few days.  If you don't have a second language (computer
languages don't count), recruit a friend who does.

cjl

On Thu, Sep 8, 2011 at 2:54 AM, Simon Schampijer <simon at schampijer.de> wrote:
> Hi,
>
> we are still on track in our 0.94 development cycle [1]. The release is
> three weeks away from now, we plan to release the 28th of September!
>
> We have been entering string freeze now, which means: "No string changes may
> be made without confirmation from the localization team and notification to
> the release team" [2]. This freeze is meant to help the translators finish
> their work and to not provide them with a moving target. Now is the time we
> will see a lot of commits from our great translators community, Activity
> developers please watch out for those and do make releases to make that work
> available.
>
> There have been one interesting string change in the last week: there are
> two entries in the sugar.po that translate the same string ('Remove') but
> where the context is different. This has been marked now using pgettext.
> Chris has pulled that change to Pootle and all langs sugar.po have been
> refreshed. An example can be seen at [3][4]. Please give feedback if that
> addition was helpful to do a better translation or if anything can be
> improved.
>
> Manuel is currently working on polishing up the tabbing experience in
> Browse. There is one string change and a significant UI change [5]. Both
> need to be discussed following the exception process [6].
>
> So what's left to be done besides translating?
>
> Right, bug fixing and testing!
>
> I have been listing Features and changes on the pre-release-notes [7] which
> should give a good sense of the bigger changes that needs testing. General
> functionality testing like (networking, saving etc) are of course welcome. I
> will add a list as well of the bugs we fixed so potential regressions in
> those areas can be identified. Watch out for more details here. There are
> instructions on the page as well how to test and where to file bugs.
>
> Three more weeks to go, let's make this a rock-solid, innovative and
> fun-to-use release.
>
> Regards,
>   Simon
>
> [1] http://wiki.sugarlabs.org/go/0.94/Roadmap#Schedule
> [2] http://wiki.sugarlabs.org/go/Development_Team/Release#String_Freeze
> [3] Remove - clipboard
> http://translate.sugarlabs.org/es/glucose/sugar.po?item=247&view_mode=translate
> [4] Remove - volume
> http://translate.sugarlabs.org/es/glucose/sugar.po?item=369&view_mode=translate
> [5]
> http://lists.sugarlabs.org/archive/sugar-devel/2011-September/033229.html
> [6] http://wiki.sugarlabs.org/go/Development_Team/Release#UI_Freeze and
> http://wiki.sugarlabs.org/go/Development_Team/Release#String_Freeze
> [7] http://wiki.sugarlabs.org/go/0.94/Notes
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>