[Gluster-devel] Congrats, your patch got MERGED. But you're not finished yet!

[Atin Mukherjee]

I've been personally following the same model while working on upstream
bugs. IMO, this needs no additional effort but just the discipline.
Because of lack of transition of bug states, our upstream BZ statistics
doesn't show the exact state where we are in now. I am pretty sure
numbers will look really promising if we follow this practice.

~Atin

On 03/30/2015 01:50 PM, Niels de Vos wrote:
> Hi all,
> 
> it's great to see that there are so many changes getting merged before
> the 3.7 release. Unfortunately it is very difficult to keep track of all
> the features that have all their patches merged, and the features that
> still have some patches that need to be reviewed.
> 
> Developers should be aware how/when the status of a bug needs to change.
> At the time patches get sent to Gerrit, the status of the associated bug
> should be POST. Once all patches for that bug have been merged, the
> developer (with the maintainers as weak backup) should move the status
> of the bug to MODIFIED.
> 
> The complete tree of 3.7 blocker bugs is here, and only very few bugs
> are in status MODIFIED:
> 
>     https://bugzilla.redhat.com/showdependencytree.cgi?id=glusterfs-3.7.0
> 
> If you have features/bugs that still need work for the 3.7 release,
> please add "glusterfs-3.7.0" in the "blocks" field of your bug. This
> will automatically add the bug to the above link.
> 
> At the moment there are many bugs that have their patches merged, but
> these bugs do not have the correct status. Developers are requested to
> review their recent patches and verify the status of the bugs for these.
> This Gerrit search should help with finding your patches:
> 
>     http://review.gluster.org/#/q/status:merged+owner:self,n,z
> 
> We also have http://bugs.cloud.gluster.org/ that shows all the open bugs
> and the status of the associated patches (review status). The column
> shows three letters (M, A and N) for the changes that have been posted:
> 
>    M = Modified
>    A = Abandoned
>    N = New
> 
> The most helpful options on http://bugs.cloud.gluster.org/ are the 'In
> Progress, but all Merged' and 'Ready For Review' selections.
>  [http://bugs.cloud.gluster.org/ updates nightly, data is not real-time]
> 
> Please have a look at the status of the bugs where you filed changes,
> and update the status appropriately.
> 
> Thanks,
> Niels and all other people checking the status of bugs.
> 
> 
> 
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
> 

-- 
~Atin