On Wed, Jun 21, 2017 at 9:12 PM, Shyam <srang...@redhat.com> wrote: > On 06/21/2017 11:37 AM, Pranith Kumar Karampuri wrote: > >> >> >> On Tue, Jun 20, 2017 at 7:37 PM, Shyam <srang...@redhat.com >> <mailto:srang...@redhat.com>> wrote: >> >> Hi, >> >> Release tagging has been postponed by a day to accommodate a fix for >> a regression that has been introduced between 3.11.0 and 3.11.1 (see >> [1] for details). >> >> As a result 3.11.1 will be tagged on the 21st June as of now >> (further delays will be notified to the lists appropriately). >> >> >> The required patches landed upstream for review and are undergoing >> review. Could we do the tagging tomorrow? We don't want to rush the >> patches to make sure we don't introduce any new bugs at this time. >> > > Agreed, considering the situation we would be tagging the release tomorrow > (June-22nd 2017). >
Status of afr/ec patches: EC patch on master: https://review.gluster.org/17594 EC patch on release-3.11: https://review.gluster.org/17615 Master patch is already merged, and 3.11 patch: https://review.gluster.org/17602 DHT patch: https://review.gluster.org/17595, I guess this patch needs review as well as regression results. At the moment we are awaiting regression results of all these patches. > > >> >> >> Thanks, >> Shyam >> >> [1] Bug awaiting fix: >> https://bugzilla.redhat.com/show_bug.cgi?id=1463250 >> <https://bugzilla.redhat.com/show_bug.cgi?id=1463250> >> >> "Releases are made better together" >> >> On 06/06/2017 09:24 AM, Shyam wrote: >> >> Hi, >> >> It's time to prepare the 3.11.1 release, which falls on the 20th >> of >> each month [4], and hence would be June-20th-2017 this time >> around. >> >> This mail is to call out the following, >> >> 1) Are there any pending *blocker* bugs that need to be tracked >> for >> 3.11.1? If so mark them against the provided tracker [1] as >> blockers >> for the release, or at the very least post them as a response to >> this >> mail >> >> 2) Pending reviews in the 3.11 dashboard will be part of the >> release, >> *iff* they pass regressions and have the review votes, so use the >> dashboard [2] to check on the status of your patches to 3.11 and >> get >> these going >> >> 3) Empty release notes are posted here [3], if there are any >> specific >> call outs for 3.11 beyond bugs, please update the review, or >> leave a >> comment in the review, for us to pick it up >> >> Thanks, >> Shyam/Kaushal >> >> [1] Release bug tracker: >> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.11.1 >> <https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.11.1> >> >> [2] 3.11 review dashboard: >> https://review.gluster.org/#/projects/glusterfs,dashboards/d >> ashboard:3-11-dashboard >> <https://review.gluster.org/#/projects/glusterfs,dashboards/ >> dashboard:3-11-dashboard> >> >> >> [3] Release notes WIP: https://review.gluster.org/17480 >> <https://review.gluster.org/17480> >> >> [4] Release calendar: >> https://www.gluster.org/community/release-schedule/ >> <https://www.gluster.org/community/release-schedule/> >> _______________________________________________ >> Gluster-devel mailing list >> gluster-de...@gluster.org <mailto:gluster-de...@gluster.org> >> http://lists.gluster.org/mailman/listinfo/gluster-devel >> <http://lists.gluster.org/mailman/listinfo/gluster-devel> >> >> _______________________________________________ >> maintainers mailing list >> maintain...@gluster.org <mailto:maintain...@gluster.org> >> http://lists.gluster.org/mailman/listinfo/maintainers >> <http://lists.gluster.org/mailman/listinfo/maintainers> >> >> >> >> >> -- >> Pranith >> > -- Pranith
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
