On 14/07/2014, at 4:20 PM, Anders Blomdell wrote: > On 2014-07-14 16:03, Vijay Bellur wrote: >> Hi All, >> >> I intend creating the 3.6 branch tomorrow. After that, the branch >> will be restricted to bug fixes only. If you have any major patches >> to be reviewed and merged for release-3.6, please update this >> thread. > Does this mean that https://bugzilla.redhat.com/show_bug.cgi?id=1113050 > has no chance to get in (no patch for that yet, still trying to figure out > how things work inside gluster)? Sounds like that would be a bug fix, so it'd get applied to everything that it makes sense too. eg likely 3.6, 3.5, 3.7dev, etc. > I think http://review.gluster.org/8299 is important, since gluster will break > with some locales. Also a bug fix. It seems simpler to commit sooner rather than later, but it'll depend on reviews. > And I would really like to get http://review.gluster.org/8292, IPv6 support. Niels, have you had a change to look at this? Should we get this merged, and fix any bugs that turn up later? > http://review.gluster.org/8208 Seems like a bugfix, so it can likely go in after Susant and others have finished working on it. > and http://review.gluster.org/8203. Same as 8208, it looks like a bugfix. Seems further along the dev/review process. > All the things above should already be on > https://bugzilla.redhat.com/show_bug.cgi?id=1117822, so maybe this mail is just > noise. Nah, reminders are useful. :) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
