[Gluster-devel] Patch Pruning and Release Tracking

John Mark Walker johnmark at redhat.com
Fri Mar 1 14:55:28 UTC 2013


Greetings,

As we approach the beta release for GlusterFS 3.4, I wanted to share how we're tracking issues that will be merged into 3.4, and which will be deferred to 3.5 or 3.4.1.

Here is the wiki page where we're tracking this info:

http://www.gluster.org/community/documentation/index.php/PatchPruning


At the top is a link to a tracking bug in Bugzilla where we're tracking all bugs with a 3.4 dependency. The direct link to that tracking bug here:

https://bugzilla.redhat.com/showdependencytree.cgi?id=895528


The running list of commits to either "accept" or "defer" for 3.4 will change significantly, so check back frequently.

Incidentally, you can always reach this page from the Developers page (http://www.gluster.org/community/documentation/index.php/Developers ) or the 3.4 planning page (http://www.gluster.org/community/documentation/index.php/Planning34 )

Thanks - we should be set to release alpha2 Real Soon Now.

-JM




More information about the Gluster-devel mailing list