<br><br><div class="gmail_quote">On Mon, May 30, 2011 at 3:59 AM, Simon Schampijer <span dir="ltr"><<a href="mailto:simon@schampijer.de">simon@schampijer.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br>
<br>
to simplify OLPC-A's [1] ticket workflow we would like to use the SugarLabs bug tracker for tickets related to Sugar and for Activities (the hardware related issues and the issues of other components like kernel and drivers will stay at the OLPC bug tracker [2]). Currently we use mainly the OLPC bug tracker to keep track of failures and tasks for our releases. We think that it makes sense to have the bug house keeping for Sugar and Activity bugs happening at one place to not have duplicated bug reports on different bug trackers.<br>
</blockquote><div><br>+1 (if only because a bug has prevented me from being able to login and update tickets on dev.l.o for more than a year :P)<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
We would like to do two things: add a keyword for our release to the tickets we are interested in e.g. '11.2.0'. Furthermore, based on the Trac ticket workflow [3] we would like to add a new field to the Sugar Labs bug tracker: "Action Needed". This helps us to do QA and release management on our tickets. We would simplify this a bit to the following states of the "Action Needed" field:<br>
<br>
(set by developers):<br>
reproduce -- we need to know how to reproduce the issue<br>
diagnose -- diagnose root cause<br>
code -- code a fix.<br>
review -- sent a patch for review<br></blockquote><div><br>+1 <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
(set by module maintainers):<br>
package -- package it up as an RPM, an activity, etc.<br>
add to build -- package needs to be added to a development build<br></blockquote><div><br>+1 <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
(set by release manager):<br>
test in build -- package in the recent build for testing<br></blockquote><div><br>? Which build would a release manager be referring to? (We "support" multiple builds these days.) <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
(set by QA):<br>
qa signoff -- has been tested by the QA<br>
no action -- and closed.<br></blockquote><div><br>? In the context of which release would the QA team be working?<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
So far, the policy in Sugar Labs has been that a ticket is closed when the fix landed in git. As there is no organized QA in Sugar Labs and no direct final product that approach works fine and can stay in place. For the tickets we touch we would just do those extra steps. We will make sure that the tickets get closed though to not leave garbage behind.<br>
<br>
Technically the "Action Needed" field is a custom field that can be added in the administration panel.<br>
<br>
Please let me know what you think about this, if this is a workable approach, if there are any downsides with this etc.<br></blockquote><div><br>Except for clarifying the issue of multiple releases, I think this is a great idea.<br>
<br>-walter<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Regards,<br>
Simon<br>
<br>
[1] OLPCA are the guys working on images for the different XO hardware, currently the development cycle is called 11.2.0 <a href="http://wiki.laptop.org/go/11.2.0/Release_plan" target="_blank">http://wiki.laptop.org/go/11.2.0/Release_plan</a><br>
[2] <a href="http://dev.laptop.org/" target="_blank">http://dev.laptop.org/</a><br>
[3] <a href="http://wiki.laptop.org/go/Trac_ticket_workflow" target="_blank">http://wiki.laptop.org/go/Trac_ticket_workflow</a><br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Walter Bender<br>Sugar Labs<br><a href="http://www.sugarlabs.org">http://www.sugarlabs.org</a><br><br>