[Gluster-devel] 3.10 bugs

Niels de Vos ndevos at redhat.com
Fri Feb 17 15:13:41 UTC 2017

On Fri, Feb 17, 2017 at 09:54:49AM -0500, Jeff Darcy wrote:
> Please don't file bugs directly against 3.10 if they're also present
> in master.  Since the fix has to go into master first anyway, the bug
> should be filed against that.  Subsequently, the developer is
> responsible for cloning both the bug and the patch for 3.10 if a
> backport is needed.

For bugs reported by users that do not test builds from the master
branch, we ideally follow these steps [0]:

 - read the description of the bug against 3.10
 - if this is a bug that is (most likely) still present in the master
   branch, clone it, and have the 3.10 depend on the new mainline bug
 - developers for the component get their notifications (through [1])
 - patch for the master branch get posted, reviewed merged
 - developer checks if the patch needs a backport and acts upon it

All regular contributors should be aware of this process and do the
triaging themselves when they report a new bug. The weekly bug triage
meetings on Tuesdays should only need to handle the bugs that have not
been triaged by developers responsible for the components.


[0] http://gluster.readthedocs.io/en/latest/Contributors-Guide/Bug-Triage/
[1] https://github.com/gluster/glusterdocs/blob/master/Developer-guide/Bugzilla%20Notifications.md
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20170217/6169952c/attachment.sig>

More information about the Gluster-devel mailing list