[Sugar-devel] Sugar on Fedora and Sugar on a Stick QA Processes Announcement

Simon Schampijer simon at schampijer.de
Wed Sep 22 10:41:27 EDT 2010

Hi Peter,

these are just excellent news indeed!

On 09/22/2010 10:50 AM, Peter Robinson wrote:
> Hi All,
> As some of you know I was at FUDCon Zurich last weekend. I took the
> opportunity to sit down with Adam Williamson who is in charge of the
> Fedora QA team and process to discuss how we could incorporate Sugar
> and SoaS testing into the QA process.


> Adam agreed that we would be able to incorporate Sugar into the
> Desktop QA which will expand our testing massively as Fedora has a
> great QA team. It will also have the ability to allow us to block a
> release if there is things broken. That is a double edged sword as if
> its broken we'll also need to pull out all stops to ensure it is fixed
> as well, but overall I believe that is positive!

Of course visibility does demand responsibility as well. But I agree, 
this is positive.

> In the short term this won't affect this release too much but I will
> be spending some time to define the criteria for Alpha, Beta and Final
> releases. It will also mean we have official spins for each of the
> Alpha, Beta as well as the usual Final releases. While we will see the
> start of the benefits for the home run this will really start to kick
> in for the SoaSv5 release process.

I would be interested in these criteria too. I want to draft a new 
schedule for 0.92 in the next days. Knowing when the downstreams are 
expecting delivery will help there.

> Overall I think this is a massively positive opportunity for Sugar as
> it opens it out more to the wider Fedora community and allows us to
> get involved in the Fedora QA more and define what is important for us
> for our releases and allows us to ride on the coattails and gain the
> benefit of the awesome work that Adam and his team are doing upstream.

It will be interesting to see how we can share the QA resources (testing 
plans). I think there are basic tests the upstream and each downstream 
is interested in. I hope the interested people will sit together and 
find good ways of working together on this.

I think we need someone at Sugar Labs that "coordinates" the QA efforts. 
 From a release management point of view we really lack that. If there 
is someone that wants to spend a few hours per month on working on this 
- now might be a good moment to speak up.


More information about the Sugar-devel mailing list