[Sugar-devel] [ANNOUNCE] Sucrose 0.84 Feature Freeze
simon at schampijer.de
Fri Dec 19 14:45:01 EST 2008
Greg Smith wrote:
> Hi Simon,
> Thanks for the follow up! You are definitely welcome at every 9.1
> planning meeting as is everybody who is interested in working on the
> next major software release for the XO. Consider yourself personally
> invited :-)
> I added a line to the 9.1.0 schedule to note 0.83 freeze. See:
> That schedule needs a lot of work which I hope we can track in our
> weekly meeting.
> On this:
> > dev.laptop.org should have bugs that are only relevant to the OLPC
> > platform in the future. Currently, I guess there are still some bugs
> > that other distributions would profit as well
> I'm still not quite clear. Let me ask it this way. I want to list,
> triage, prioritize and track all the important bugs for XO Software
> Release 9.1.0. That includes the Sugar bugs. Which trac system do I use
> for that? Maybe both?
En gros: So, bugs that are unique to the OLPC distribution should go
into OLPC trac. Other bugs should be filed upstream - in sugarlabs.org
trac. This has the advantage that other distribution are aware of this
as well and - more eyes watching, better chance it gets fixed.
Then there are different ways of tracking. You could file a bug at olpc
trac and that then traces the changes of the upstream bug for example.
We discussed different ways it in our last BugSquad meeting
http://sugarlabs.org/go/BugSquad/Meetings/Minutes/2008-12-17. I am sure
we will figure out the details with mel in the upcoming weeks.
> On release notes, features and this:
> > Time left is short for this release. What we are currently working on
> > can be seen in our development TODO list
> > http://sugarlabs.org/go/DevelopmentTeam/TODO.
> Our QA needs to know what bugs and features will be in the release
> before the release is done in order to be able to test them in advance.
> If I understand correctly, you only post the feature list in the release
> notes after its final.
We have 6 to stabilize weeks after feature freeze. I hope that this is a
decent amount of time to do the testing. By then, you know for sure what
features are exactly in. If you want to start testing before, you need
to take the information provided in the release announcements - those
list all the fixes that went in.
> Where can I get a list of things that QA (volunteer or otherwise) should
> test before we finish?
> Let me know if those questions are not clear or you need any more info.
> BTW I'm not complaining. Your documentation is definitely getting better
> and I appreciate the work everyone is doing. I'm just trying to work out
> the details so we can make another quality release.
Sure, please keep asking.
> Greg S
> PS - Should this thread be on the OLPC devel list? Can you post your
> Sugar announcements stuff to that list? That way I can reply there and
> try to conform to Tomeu's list usage strictures.
> (kidding about "strictures" T-man, I'm just trying to do the right thing
> Simon Schampijer wrote:
>> Greg Smith wrote:
>>> Hi Simon,
>>> I looked at the schedule. Its helpful but I'm not sure I fully
>>> understand all the milestones.
>>> What is the definition of "final release"?
>> This is the golden image. It is the last coordinated release. After
>> that we only deliver updates for components.
>>> Once the feature set is frozen, how do I know what is in the release?
>> Each release in the cycle has it's release page with the relevant
>> features and fixes for the specific release. After Feature Freeze we
>> might wrap up what big changes/features went in, in the announcement.
>>> that the list of Trac IDs in 0.83.1 release notes?
>> Would be the sum of the releases in the cycle before the feature freeze.
>> (btw the bug ID URLs
>>> on that page link to the wrong Trac system).
>>> Also, are all XO relevant bugs tracked in the OLPC Trac bug system:
>> dev.laptop.org should have bugs that are only relevant to the OLPC
>> platform in the future. Currently, I guess there are still some bugs
>> that other distributions would profit as well.
>>> Are you joining our weekly 9.1.0 meeting (Wed. at 2PM US ET IRC on
>>> freenode.net #olpc-meeting)?
>> I take this as an invitation - and will try :)
>>> I don't have it on the schedule for this week but I think we should
>>> put a "synch up with Sugar schedule" discussion on the agenda ASAP.
>> Time left is short for this release. What we are currently working on
>> can be seen in our development TODO list
>>> Stability is a top priority for XO users. The only way I know of to
>>> improve stability is lots of testing time and focus on bug fixes. We
>>> need to get that scheduled soon if we want a new sugar release in XO
>>> Software Release 9.1.0 in March.
>> That is why we set the feature freeze in mid January - that we have 6
>> weeks left to stabilize. By January I hope to have the BugSquad 
>> then in place to handle all the incoming bug reports from testing.
>>> My impression is that we made a big step forward on improving
>>> stability in 8.2.0. I hope we can do it again.
>> Sure :)
>>> Greg S
>>  http://sugarlabs.org/go/BugSquad
More information about the Sugar-devel