On Mon, May 29, 2017 at 8:01 PM, Shyam <srang...@redhat.com> wrote: > On 05/25/2017 05:23 PM, Shyam wrote: > >> Hi, >> >> If your name is on the following list, we need your help in updating the >> release notes and thus closing out the final stages of 3.11 release. >> Please do the needful by end of this week! (which means there is single >> day remaining, unless you intend to do this over the weekend) >> >> @pranith, @spalai, @kotresh, @niels, @poornima, @jiffin, @samikshan, >> @kaleb >> > > I am yet to receive updates for 4 issues as below, I am writing the > release notes for these myself (within the next 2 hours possibly), and > adding appropriate members for review. There is a chance that the patch may > get merged before you have a chance to review the same, so if there are any > technical accuracy issues, it would have to be corrected asynchronously. > > Team, we need to practice writing specs/release-notes by the time of branching itself. Because if you postpone them, last minute there will be one or the other thing comes up making the feature not complete.
I like the idea of writing release-notes before starting a feature. It helps to get the feature done as per the specs. This approach is followed in some of the projects, i heard. > 3) Distritbute: [RFE] More robust transactions during directory >> namespace operations. (@kotresh) (#191) >> > > 4) bitrot: [RFE] Enable object versioning only if bitrot is enabled. >> (@kotresh) (#188) >> > > 5) New xlator to help developers detecting resource leaks (@niels) (#176) >> > > 8) SELinux support for Gluster Volumes (@niels @jiffin) (#55) >> > > Shyam > > "Releases are made better together" > > :-) -Amar > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-devel > -- Amar Tumballi (amarts)
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel