On Tue, Jul 26, 2016 at 10:35:51AM +0530, Kaushal M wrote: > Hi all! > > The GlusterFS-3.6 series has been around for nearly 2 years now. The > first 3.6.0 release happened late October 2014. We've had 9 releases > since then, with latest release 3.6.9 happening in early March 2016. > There hasn't been any activity on the release-3.6 branch since then. > The 3.6 series is also due to be EOLed once GlusterFS-3.9 is released > (which is currently being targetted for a October 2016 release). > > As we haven't been having regular 3.6 releases for a while, and as the > release of 3.9 is close, we've decided to officially not do anymore > 3.6 releases. Till 3.9 gets released, 3.6 will only get fixes for > security and critical issues. If anyone has such issues, please bring > it to out notice. There are still some patches under review for 3.6: http://review.gluster.org/#/q/status:open+project:glusterfs+branch:release-3.6 I have abandonded the ones I sent, and closed the related bugs with a not. See these links for an example: http://review.gluster.org/14771 https://bugzilla.redhat.com/show_bug.cgi?id=1208384 There are currently 119 bugs open with a 3.6.x version: https://bugzilla.redhat.com/buglist.cgi?f1=bug_status&f2=version&o1=notequals&o2=regexp&product=GlusterFS&v1=CLOSED&v2=^3.6 Someone (or rather a few people) need to volunteer to go through the bugs and close them with a note, or change the version to something more appropriate. Any of the bugs that are assigned already, should probably be checked by the person who owns the bug. Thanks, Niels
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
