<p dir="ltr">In our Jira workflow we have different states like: Open, In Progress, Review, Landing and etc.<br>
It is engineer responsibility to maintain correct state.<br>
After engineer see that it has two +1, he/she transfers ticket to state Landing.<br>
Gatekeeper has search for all tickets at this state and see what is ready to land. Actually gatekeeper (or other people) could subscribe to search and receive e-mail with it results.</p>
<p dir="ltr">Having different states in Jira gives us more clear vision what is the state of the project and where issues are.<br>
Using Kanban GreenHopper RapidBoard you even could get many statistical info about time that was spend in each state and other charts/stat.</p>
<p dir="ltr">Limiting work in progress in each state you could easily see where you having issues in process. BTW our UpstreamLanding column is always red, that's why we always trying to find a way to improve process of upstream landing.</p>
<p dir="ltr">Kanban def: <a href="http://www.infoq.com/resource/minibooks/kanban-scrum-minibook/en/pdf/KanbanAndScrumInfoQVersionFINAL.pdf">http://www.infoq.com/resource/minibooks/kanban-scrum-minibook/en/pdf/KanbanAndScrumInfoQVersionFINAL.pdf</a><br>
<a href="https://www.atlassian.com/software/greenhopper/overview/kanban">https://www.atlassian.com/software/greenhopper/overview/kanban</a></p>
<p dir="ltr">Maybe having RapidBoard at Intel Jira with such info for sustaining will give to all of us more visibility and stat. But that requires Jira workflow changes and process changes.<br>
</p>
<div class="gmail_quote">On Aug 3, 2013 1:27 AM, "Christopher J. Morrone" <<a href="mailto:morrone2@llnl.gov">morrone2@llnl.gov</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks Denis, those are some great leads!<br>
<br>
I think it would be excellent to investigate one or both of those links to get gerrit enhanced to match our workflow. I opened ticket LU-3690 as a task to track this.<br>
<br>
I like the sounds of the prolog-cookbook approach. But I see what you mean, it is not clear to me that making a patch "submitable" is sufficient to give us something that we can use as search term. So that may make the perl "hook for a +2 approval from a simple quorum of +1 votes" a better option.<br>
<br>
I am not sure that I understood your final comment about a Jira "Landing" state.<br>
<br>
Chris<br>
<br>
On 08/02/2013 04:13 AM, Denis Kondratenko wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Chris,<br>
<br>
I see your point now. We are not using gerrit with a way it was designed<br>
for (when +2 should be there to submit; seems our gatekeepers doing +2).<br>
You are right it is impossible to build search for gatekeeper from plain<br>
gerrit without it modification.<br>
<br>
There are still some ways to workaround that:<br>
* <a href="http://en.wikibooks.org/wiki/Git/Gerrit_Code_Review" target="_blank">http://en.wikibooks.org/wiki/<u></u>Git/Gerrit_Code_Review</a> (A hook could -<br>
for instance - allow a project to install an automated gatekeeper to<br>
vote +2 'submit approved' when sufficient +1 votes 'looks good to me'<br>
have been received)<br>
*<br>
<a href="http://review.whamcloud.com/Documentation/prolog-cookbook.html#_example_12_1_1_2_code_review" target="_blank">http://review.whamcloud.com/<u></u>Documentation/prolog-cookbook.<u></u>html#_example_12_1_1_2_code_<u></u>review</a> (but<br>
I don't know if it will get right searches..)<br>
* in Xyratex we are using Jira state "Landing" to build filter for<br>
gatekeeper.<br>
<br>
OK, even if we could't separate gatekeeper changes from other, filter is<br>
still useful to check issues with no feedback for a long time.<br>
<br>
Thanks,<br>
Denis<br>
<br>
<br>
------------------------------<u></u>------------------------------<u></u>------------<br>
For additional information including the registered office and the treatment of Xyratex confidential information please <a href="http://visitwww.xyratex.com" target="_blank">visitwww.xyratex.com</a> <<a href="http://www.xyratex.com/" target="_blank">http://www.xyratex.com/</a>><br>
<br>
------------------------------<u></u>------------------------------<u></u>------------<br>
<br>
<br>
______________________________<u></u>_________________<br>
cdwg mailing list<br>
<a href="mailto:cdwg@lists.opensfs.org" target="_blank">cdwg@lists.opensfs.org</a><br>
<a href="http://lists.opensfs.org/listinfo.cgi/cdwg-opensfs.org" target="_blank">http://lists.opensfs.org/<u></u>listinfo.cgi/cdwg-opensfs.org</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
cdwg mailing list<br>
<a href="mailto:cdwg@lists.opensfs.org" target="_blank">cdwg@lists.opensfs.org</a><br>
<a href="http://lists.opensfs.org/listinfo.cgi/cdwg-opensfs.org" target="_blank">http://lists.opensfs.org/<u></u>listinfo.cgi/cdwg-opensfs.org</a><br>
</blockquote></div>
<br>
<pre style="white-space:pre-wrap;color:rgb(34,34,34);background-color:rgb(255,255,255)"><hr>For additional information including the registered office and the treatment of Xyratex confidential information please visit <font color="#1155cc"><a href="http://www.xyratex.com/" target="_blank">www.xyratex.com</a></font>
</pre><div><hr></div>