Open Stack

2015-02-03 22:40 GMT+08:00 Eduard Matei <eduard.matei at cloudfounders.com>:

>
> Hi team,
>
> We have some questions regarding the Gerrit workflow and what should we do
> next for our patch to be merged:
> 1. Once we have a CodeReview +2 and a Jenkins Verified +1 what should we
> do next to get the patch merged?
>
    We need at least two code review + 2 and will approved by core
reviewer.

> 2. If we have a CodeReview +2 and we want to fix an issue, does the next
> patchset keep the CR +2 ?
>
    will not keep +2 if change code except a rebase.

> 3. Once the patch is merged, if we have further changes do we have to
> create a new patch (blueprint/bug report)?
>
   Yes ,need another commit ( bug or blueprint report)

>
> Thanks,
> Eduard
>
> --
>
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com
>  | eduard.matei at cloudfounders.com
>
>
>
> *CloudFounders, The Private Cloud Software Company*
>
> Disclaimer:
> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
> If you are not the named addressee or an employee or agent responsible for delivering this message to the named addressee, you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this email in error we request you to notify us by reply e-mail and to delete all electronic files of the message. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
> E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the content of this message, and shall have no liability for any loss or damage suffered by the user, which arise as a result of e-mail transmission.
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
ChangBo Guo(gcb)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150203/1c77fb18/attachment.html>