<div>
Really awesome stuff, thank you guys!</div><div><div><br></div><div>John Postlethwait</div><div>Nebula, Inc.</div><div>206-999-4492</div><div><br></div></div>
<p style="color: #A0A0A8;">On Thursday, June 7, 2012 at 3:46 PM, Monty Taylor wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>Hey guys!</div><div><br></div><div>We just upgraded to a new version of gerrit. This is based on the new</div><div>upstream version 2.4, but in addition we've landed two additional</div><div>features on top of that - so there's tons of new toys to play with.</div><div><br></div><div>First of all, in 2.4 upstream has added a new button "Rebase Change" ...</div><div>which you can use to rebase your change on top of the current tip of the</div><div>target branch from within gerrit itself. Also, upstream has been working</div><div>on adding a proper REST interface, instead of json-rpc which is what</div><div>they have been using. I'm not sure how far that's gotten, but I believe</div><div>it can do a decent amount of stuff for those of you who like, you know,</div><div>REST-based scripting.</div><div><br></div><div>In addition to that, we've got two main features we've landed as well.</div><div><br></div><div>David Shrewsbury wrote a long-requested feature: a Work In Progress</div><div>state. Changes will now have a Work In Progress button on them that can</div><div>be used to mark the change as something that the dev is working on</div><div>again, so that other folks know they don't need to review it. The button</div><div>is available to the author of the patch, as well any group that we</div><div>assign to have access. In our case, we'll be granting $project-core Work</div><div>In Progress permission. Putting something back into the "ready for</div><div>review" state can be done one of two ways - either by just uploading a</div><div>new patch to the change, or by clicking the "Ready for Review" button.</div><div><br></div><div>Hand in hand with that change, Clark Boylan has written an "Important</div><div>Changes" view - which shows all on one page the changes that a developer</div><div>should be looking at. On the page are changes that were uploaded by the</div><div>developer (same as the "My Changes" page), then a section for changes</div><div>that the developer should be reviewing, which are changes that the dev</div><div>has either watched, starred, or that reviews have been requested, and</div><div>that are no in work in progress state and additionally that the dev has</div><div>not already reviewed. Finally, there is a section for changes that the</div><div>developer has already reviewed, in case they need to be further tracked.</div><div><br></div><div>We're hoping that some of these things help to reduce a little bit of</div><div>the burden in terms of tracking which things should be watched. We'll be</div><div>working on getting our patches upstreamed in the near future... but</div><div>since they are new workflow possibilities, we're happy to get feedback</div><div>on ways in which they could be more useful to folks.</div><div><br></div><div>Also - we have an open question - which is, if the pre-approval check</div><div>jobs fail in Jenkins, should the patch be automatically marked Work In</div><div>Progress. We're not going to do that right out of the gate, but would</div><div>love feedback on what people think.</div><div><br></div><div>Thanks everybody!</div><div>Monty</div><div><br></div><div>_______________________________________________</div><div>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a></div><div>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a></div><div>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a></div><div>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>