openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #10034
Re: New Gerrit version (and server)
-
To:
openstack@xxxxxxxxxxxxxxxxxxx
-
From:
Thierry Carrez <thierry@xxxxxxxxxxxxx>
-
Date:
Fri, 13 Apr 2012 13:31:44 +0200
-
In-reply-to:
<1334313063.18923.43.camel@sorcha>
-
Organization:
OpenStack
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120410 Thunderbird/11.0.1
Mark McLoughlin 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?
I'll definitely look into that possibility... Depends a bit on the
security model around drafts (not being listed is not the same as being
private).
--
Thierry Carrez (ttx)
Release Manager, OpenStack
Follow ups
References