[IAEP] Proposal release management

Simon Schampijer simon at schampijer.de
Thu Jun 24 03:32:34 EDT 2010


in May I tried to find someone to replace me as release manager [1] for 
0.90, but as nobody has stepped up to do the job as we defined it I 
decided that it will be best to keep this role for some more time. I 
think it will be important for Sugar that we keep some continuation of 
the processes that we have been setting up during the last years. It 
would also be very good if someone would like to lend a hand with this 
or shadow me for future tasks so more people in Sugar Labs have direct 
hands-on knowledge.

We defined the role of the release manager in the past 3 releases like 
the following:

* setting the schedule
* make sure that the Feature process is followed by the submitters [2]
* keeping the wiki updated about the released modules and making sure to 
have final release notes available
* sending email reminders about approaching Freezes, tarball due dates etc

The schedule would be based on the GNOME releases, a 6 month release 
cycle. As there is not much time left for 0.90 [3] I think we should 
mainly focus on stabilizing and landing the features that were left over 
from the last release. I would start to announce a time frame for future 
releases so that future development can go on. New Features would be 
handled by the Feature process, as it has been the case in the past.

What do others think about this?


[1] http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023710.html
[2] http://wiki.sugarlabs.org/go/Features/Policy
[3] http://wiki.sugarlabs.org/go/0.90/Roadmap

More information about the IAEP mailing list