search for: 1463250

...hes 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. > > Thanks, > Shyam > > [1] Bug awaiting fix: 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. >> &g...

...ches 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). > > > > 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 >...

...s 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...

...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). Thanks, Shyam [1] Bug awaiting fix: 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,...

...ing, > > 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 > I added https://bugzilla.redhat.com/show_bug.cgi?id=1463250 as blocker just now for this release. We just completed the discussion about solution on gluster-devel. We are hoping to get the patch in by EOD tomorrow IST. This is a geo-rep regression we introduced because of changing node-uuid behavior. My mistake :-( > > 2) Pending reviews in the 3.11...

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