Thanks James and team for the work here, this will be very useful for documentation drafts. <br><br><div style="text-align:left">Anne<br></div><br><div class="gmail_quote">On Fri, Apr 13, 2012 at 8:55 AM, Sandy Walsh <span dir="ltr"><<a href="mailto:sandy.walsh@rackspace.com">sandy.walsh@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sounds awesome! Looking forward to Draft Changes, much needed.<br>
<br>
-S<br>
<br>
<br>
________________________________________<br>
From: openstack-bounces+sandy.walsh=<a href="mailto:rackspace.com@lists.launchpad.net">rackspace.com@lists.launchpad.net</a> [openstack-bounces+sandy.walsh=<a href="mailto:rackspace.com@lists.launchpad.net">rackspace.com@lists.launchpad.net</a>] on behalf of James E. Blair [<a href="mailto:corvus@inaugust.com">corvus@inaugust.com</a>]<br>
Sent: Thursday, April 12, 2012 8:23 PM<br>
To: OpenStack Mailing List<br>
Subject: [Openstack] New Gerrit version (and server)<br>
<div class="HOEnZb"><div class="h5"><br>
Hi,<br>
<br>
We've just upgraded Gerrit to version 2.3. There are a lot of changes<br>
behind the scenes that we've been looking forward to (like being able to<br>
store data in innodb rather than myisam tables for extra data<br>
longevity). And there are a few visible changes that may be of interest<br>
to OpenStack developers.<br>
<br>
One new addition in 2.3 is "draft changes". The idea behind a draft<br>
change in Gerrit is that it is a change that is not ready for merging,<br>
or even general code review, but you would like to share it with some<br>
people to get early comments. If you upload a change as a draft, by<br>
default, no one else can see it. You must explicitly add each person<br>
you would like to share it with as a reviewer. Reviewers you add can<br>
leave comments, but can not vote at this stage. You can continue to<br>
upload new patchsets to the change as it evolves, and once it is ready<br>
for general review, you can click the "Publish" button. It will then<br>
become a normal change in Gerrit that everyone can see, including the<br>
earlier reviews from the draft stage. This is a one way transition;<br>
once a draft is published, it can't be made a draft again.<br>
<br>
If you're using git-review from source or the latest version from PyPI<br>
(version 1.16, released today), you can easily upload a draft change by<br>
adding the "-D" option (eg, "git review -D"). Earlier versions of<br>
git-review also have the "-D" option, but the git ref that Gerrit uses<br>
to indicate a change should be a draft was changed between the 2.3<br>
release candidate and the final release; so if using "-D" results in an<br>
error, you may need to upgrade.<br>
<br>
You may notice some changes to the diff view. Notably, the header which<br>
contained all of the possible viewing options has been split up into<br>
several parts; you can switch between them by selecting options that<br>
show up under the menu at the top. I recommend setting "Retain Header<br>
On File Switch" under the Preferences section, as it is a nicer<br>
experience when changing files.<br>
<br>
Another notable new feature is the ability to add a group to the list of<br>
reviewers for a change. Just type in the name of the group and click<br>
"Add Reviewer" and all of the individuals in the group will be added to<br>
the list of reviewers (and will see the change on their "review<br>
requests" list.<br>
<br>
Finally, we've modified some of our local OpenStack style changes so<br>
that it is easier for us to track upstream changes in layout. It should<br>
mean a little more consistency throughout the interface, though we<br>
weren't able to keep the alternating row colors on the main table<br>
without a disproportionate amount of effort. Do note that you can click<br>
on a line in a table, and it will be highlighted to improve legibility.<br>
<br>
We've tried to give this as much testing as possible before moving it<br>
into production. If you encounter any issues, please let us know on IRC<br>
(mtaylor, jeblair, LinuxJedi), via email at<br>
<<a href="mailto:openstack-ci-admins@lists.launchpad.net">openstack-ci-admins@lists.launchpad.net</a>>, or you can file a bug at:<br>
<br>
<a href="https://bugs.launchpad.net/openstack-ci/" target="_blank">https://bugs.launchpad.net/openstack-ci/</a><br>
<br>
Thanks,<br>
<br>
Jim<br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</div></div></blockquote></div><br>