[etoys-dev] 4.1.1 schedule?

[Bert Freudenberg]

On 30.09.2010, at 02:57, Bert Freudenberg wrote:

> On 30.09.2010, at 04:51, Korakurider wrote:
> 
>> On Thu, Sep 30, 2010 at 10:48 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>>> On 30.09.2010, at 03:08, Korakurider <korakurider at gmail.com> wrote:
>>> 
>>>> 2010/9/30 Bert Freudenberg <bert at freudenbergs.de>:
>>>>> Unfortunately, this report came too late for the 4.1 release. But we will likely do a 4.1.1 release in a few weeks, which will have the fix.
>>>> 
>>>> Let's discuss the schedule.
>>>> 4.1 was targeted to SL's specific release.
>>>> Do we have similar milestone for 4.1.1?
>>> 
>>> Yes, Sugar will have an update too:
>>> 
>>> http://wiki.sugarlabs.org/go/0.90/Roadmap
>> 
>> So due date for our release is
>> Oct25 (for Sucrose 0.90.1 Bugfix Release tarballs), right?
>> 
>> btw, we might want to plan similar schedule for 4.1.1 and future release.
>> 
>> /Korakurider
> 
> Yes. I'm too lazy to maintain our own copy of the schedule, so I'm just referring to the Sugar one. It would be great if you could make (and maintain) an Etoys schedule.
> 
> The next Sugar schedule has not been published yet.

It is published now. I suggest we follow it - so the next Etoys release would be in April 2011:
http://wiki.sugarlabs.org/go/0.92/Roadmap#Schedule

- Bert -

> But it will probably follow the Gnome schedule again. Gnome was announced to be released in March 2011. As you can see, the Sugar dates and Gnome dates for this release were the same:
> http://live.gnome.org/TwoPointThirtyone
> 
> For our "bugfix" release at the end of October we only let in really important fixes, no new features. And translation updates, but that's all.
> 
> We need to decide if we need to branch now. That would mean making an "etoys41" MC repository exclusively for the bug fix release. Regular development work would continue in the "etoys" repo. OTOH, since the release is built using explicit configuration maps in the update stream, we don't necessarily have to have a new repository now. 
> 
> So people should feel free to start working now in the "etoys" repository again.
> 
> Oh, something else: we need a new dev image. It's not strictly necessary of course. With Etoys-To-Go you can just disable the "etoy friendly" preference and save the image. There is your dev version. However, it would be good to have a dev image  with full change history going back all the way to the original Etoys 4.0 image ... In the mean time, just a current Etoys-Dev download like I used to make previously would be good. Anybody interested in making that?
> 
> - Bert -