Re: Development work flow

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/05/2013 01:14 AM, Anand Avati wrote:
I have added a new section "Submission Disqualifiers" clarifying the
meaning of negative votes in Gerrit.

http://www.gluster.org/community/documentation/index.php/Development_Work_Flow#Submission_Disqualifiers



Just wanted to mention few more updates which Avati introduced to the workflow

* rh-bugs tests for every patch :
From now on, patches with bug id not belonging to GlusterFS product in Red Hat Bugzilla [1] will fail with -1 vote in verify section. This is a step in the direction to reduce possible mistakes of giving a Bug Id for a patch with 'private' or 'restricted' bugs. Also, would prevent typos if any while entering bug id.

* Review posts update comment in bugzilla:
Once a patch goes in to gerrit, there will be a bugzilla comment made with subject of the patch and URL in bugzilla, so reporter of the issue can take action of reviewing the patch or even testing the patch.

* Merge posts commit message of patch as comment in bugzilla:
When ever a patch gets merged to the upstream, the whole commit message will be posted as comment in bugzilla. This is done as a step to capture more details in bugzilla (ie, more detailed RCA etc). So it would be good if developers posting patches write very elaborate commit message which would help everyone to understand what was the problem the patch fixed. Future idea is to capture most of these updates in our documentation if required.

Regards,
Amar

[1] - https://bugzilla.redhat.com/buglist.cgi?product=GlusterFS




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux