[Localization] The new Sugar Roadmap and other things

[Sayamindu Dasgupta]

On Thu, Jun 5, 2008 at 7:40 AM, Korakurider <korakurider at gmail.com> wrote:
> Hi.
>
> On 6/5/08, Sayamindu Dasgupta <sayamindu at gmail.com> wrote:
>> Hello everyone,
>> As you might have already noticed elsewhere, we have a new roadmap and
>> schedule for our software stack. The timeline for the next release
>> (version 0.82) is available at
>> http://wiki.sugarlabs.org/go/ReleaseTeam/Roadmap#Timeline
>> This should make a lot of things easier for us now, with the string
>> freeze scheduled on 20th June.
> <snip>
>> Moreover, I have been considering a reshuffle in the categorization of
>> the files in Pootle, since we now have a more or less formal
>> definition of what is core and what is not (whatever is listed in
>> http://wiki.sugarlabs.org/go/ReleaseTeam/Roadmap#Fructose_Modules and
>> http://wiki.sugarlabs.org/go/ReleaseTeam/Roadmap#Glucose_Modules are
>> core, and the rest are non core). Do you think that will help ?
>
>   The existence of "Update.1" project on Pootle has been confusing to
> me.  Will we have another "branch project" for the next release, or
> will we just use "trunk project" like "Core" ?
>


Hmm.. my plan is to have something like:

Sucrose Development (containing the bleeding edge code)
Fructose Development (same as above)

Sucrose Stable (containing the last stable release)
Fructose Stable (containing the last stable release)

Extras (extra stuff, which may or may not follow the Sugar release schedule).





>
>> Also, admins, please remember to commit your translations once you
>> think they are ready to go into the official sources that we have.
>> There is no point in having translations in Pootle only ;-).
>  As we can't see what has been changed actually on Pootle, I would
> like to see more frequent push to repo (say weekly if team are so
> active :-) and we could check history there.  Will it make sense or
> more trouble ?
>
> Ofcourse it would be great to get Pootle to have the feature though :-)
>

I can automate this, but I prefer not to unless its an emergency (I
did some mass scale commits during a translation refresh release, when
new activities were being released just to pick up new translations).

Cheers,
Sayamindu





-- 
Sayamindu Dasgupta
[http://sayamindu.randomink.org/ramblings]