openstack team mailing list archive

[Mark McLoughlin <markmc@xxxxxxxxxx>]

Hey,

On Thu, 2012-04-12 at 16:23 -0700, James E. Blair wrote:

> One new addition in 2.3 is "draft changes".  The idea behind a draft
> change in Gerrit is that it is a change that is not ready for merging,
> or even general code review, but you would like to share it with some
> people to get early comments.  If you upload a change as a draft, by
> default, no one else can see it.  You must explicitly add each person
> you would like to share it with as a reviewer.  Reviewers you add can
> leave comments, but can not vote at this stage.  You can continue to
> upload new patchsets to the change as it evolves, and once it is ready
> for general review, you can click the "Publish" button.  It will then
> become a normal change in Gerrit that everyone can see, including the
> earlier reviews from the draft stage.  This is a one way transition;
> once a draft is published, it can't be made a draft again.

This sounds cool. Will the vulnerability management team use this for
embargoed security fixes?

Cheers,
Mark.