<div><br><br><div class="gmail_quote">On Mon, May 30, 2011 at 7:51 AM, Walter Bender <span dir="ltr"><<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Mon, May 30, 2011 at 8:49 AM, Simon Schampijer <span dir="ltr"><<a href="mailto:simon@schampijer.de" target="_blank">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">
<div>On 05/30/2011 02:32 PM, Walter Bender wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
On Mon, May 30, 2011 at 3:59 AM, Simon Schampijer<<a href="mailto:simon@schampijer.de" target="_blank">simon@schampijer.de</a>>wrote:<br>
<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<br>
bug tracker for tickets related to Sugar and for Activities (the hardware<br>
related issues and the issues of other components like kernel and drivers<br>
will stay at the OLPC bug tracker [2]). Currently we use mainly the OLPC bug<br>
tracker to keep track of failures and tasks for our releases. We think that<br>
it makes sense to have the bug house keeping for Sugar and Activity bugs<br>
happening at one place to not have duplicated bug reports on different bug<br>
trackers.<br>
<br>
</blockquote>
<br>
+1 (if only because a bug has prevented me from being able to login and<br>
update tickets on dev.l.o for more than a year :P)<br>
</blockquote>
<br></div>
Often things sort out by themselves!<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><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<br>
tickets we are interested in e.g. '11.2.0'. Furthermore, based on the Trac<br>
ticket workflow [3] we would like to add a new field to the Sugar Labs bug<br>
tracker: "Action Needed". This helps us to do QA and release management on<br>
our tickets. We would simplify this a bit to the following states of the<br>
"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>
<br>
</blockquote>
<br>
+1<br>
<br>
<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>
<br>
</blockquote>
<br>
+1<br>
<br>
<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>
<br>
</blockquote>
<br>
? Which build would a release manager be referring to? (We "support"<br>
multiple builds these days.)<br>
</blockquote>
<br></div>
Ok, I guess that has not been clear enough. The "Action needed" field would be only used by the OLPCA team. The release manager would be here the release manager for the OLPCA release. At the moment Daniel for the 11.2.0 release. Of course we could try to generalize this a bit more but I think this will get tricky quickly. To help making the distinction a bit better we could label the field as well "Action needed (OLPC)" or similar.<div>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
(set by QA):<br>
qa signoff -- has been tested by the QA<br>
no action -- and closed.<br>
<br>
</blockquote>
<br>
? In the context of which release would the QA team be working?<br>
</blockquote>
<br></div>
Same here. This would be Sam triaging the bugs accordingly.<br>
<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
[...]<br>
<br>
</blockquote><div>
<br>
Except for clarifying the issue of multiple releases, I think this is a<br>
great idea.<br>
</div></blockquote>
<br>
Thanks for commenting and helping me to explain, hopefully, a bit clearer,<br><font color="#888888">
Simon<br>
</font></blockquote></div><br></div></div>Makes even more sense now.<br><br>I wonder if there is some way (automated perhaps) to migrate the open Sugar-related tickets on d.l.o to b.sl.o? <br><font color="#888888"><br>-walter</font><div>
<div></div><div class="h5"><br clear="all"></div></div></blockquote><meta http-equiv="content-type" content="text/html; charset=utf-8">Although, I really like this QA workflow, I'm not sure<div>if this will prevent people from the community to follow the workflow, e.g an ''outsider'' or an activity developer that wants to close a bug or do follow-ups that require a change of state on the workflow. For starters there should be a wiki page where to document this in order to point people to the process. </div>
<div><br></div><div>In my opinion this could be yet another wall to enter sugar development.</div><div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div class="h5"><br>-- <br>Walter Bender<br>
Sugar Labs<br><a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a><br><br>
</div></div><br>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">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>
<br></blockquote></div><br></div>