similar to: Release 3.10.4: Scheduled for the 30th of June

Apologies for delay in sending mail about builds. We have packages ready for all distributions, thanks to Kaleb and Niels. As per [1] (mostly[2]): * Packages for Fedora 24 and Fedora 27 are available at [3]. * Packages for Fedora 25 and Fedora 26 are built and queued in Fedora bodhi for testing. Once pushed to testing they will be available in the Updates-Testing repo. After a nominal testing

Dear Jiffin, Would it be possible to have the following backported to 3.12: https://bugzilla.redhat.com/show_bug.cgi?id=1482064 See my mail with subject "New 3.12.7 possible split-brain on replica 3" on the list earlier this week for more details. Thank you very much. Best regards, Mabi ??????? Original Message ??????? On April 11, 2018 5:16 AM, Jiffin Tony Thottan <jthottan at

Mabi, It looks like one of the patches is not a straight forward cherry-pick to the 3.12 branch. Even though the conflict might be easy to resolve, I don't think it is a good idea to hurry it for tomorrow. We will definitely have it ready by the next minor release (or if by chance the release is delayed and the back port is reviewed and merged before that). Hope that is acceptable.

On Tue, Jun 6, 2017 at 6:54 PM, Shyam <srangana at redhat.com> 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

Hi, It's time to prepare the 3.12.8 release, which falls on the 10th of each month, and hence would be 12-04-2018 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.12.7? 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)

On 06/21/2017 11:37 AM, Pranith Kumar Karampuri wrote: > > > On Tue, Jun 20, 2017 at 7:37 PM, Shyam <srangana at redhat.com > <mailto:srangana at 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). >

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). Thanks, Shyam [1] Bug awaiting fix: https://bugzilla.redhat.com/show_bug.cgi?id=1463250 "Releases are

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

On Wed, Jun 21, 2017 at 9:12 PM, Shyam <srangana at redhat.com> wrote: > On 06/21/2017 11:37 AM, Pranith Kumar Karampuri wrote: > >> >> >> On Tue, Jun 20, 2017 at 7:37 PM, Shyam <srangana at redhat.com >> <mailto:srangana at redhat.com>> wrote: >> >> Hi, >> >> Release tagging has been postponed by a day to accommodate

Hi, It's time to prepare the 3.12.6 release, which falls on the 10th of each month, and hence would be 12-02-2018 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.12.6? 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)

Hi, It's time to prepare the 3.12.2 release, which falls on the 10th of each month, and hence would be 10-10-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.12.2? 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)

Hi, I am planning to do 3.12.2 release today 11:00 pm IST (5:30 pm GMT). Following bugs is removed from tracker list Bug 1493422 - AFR : [RFE] Improvements needed in "gluster volume heal info" commands -- feature request will be target for 3.13 Bug 1497989 - Gluster 3.12.1 Packages require manual systemctl daemon reload after install -- "-1" from Kaleb, no progress from

Hi, I wonder how this procedure works. I could add a bug that I think is a *blocker*, but there might not be consensus. Cheers, Hans Henrik On 11-01-2018 07:02, Jiffin Tony Thottan wrote: > Hi, > > It's time to prepare the 3.12.5 release, which falls on the 10th of > each month, and hence would be 12-01-2018 this time around. > > This mail is to call out the following,

On 12/10/17 16:05, Amar Tumballi wrote: > > > On Thu, Oct 12, 2017 at 3:43 PM, Mohammed Rafi K C > <rkavunga at redhat.com <mailto:rkavunga at redhat.com>> wrote: > > Hi Jiffin/Shyam, > > > Snapshot volume has been broken in 3.12 . We just got the bug, I have > send a patch [1] . Let me know your thought. > > > > Similar with

Hi Jiffin/Shyam, Snapshot volume has been broken in 3.12 . We just got the bug, I have send a patch [1] . Let me know your thought. [1] : https://review.gluster.org/18506 On 10/12/2017 12:32 PM, Jiffin Tony Thottan wrote: > Hi, > > I am planning to do 3.12.2 release today 11:00 pm IST (5:30 pm GMT). > > Following bugs is removed from tracker list > > Bug 1493422 - AFR :

On Tue, Jun 20, 2017 at 7:37 PM, Shyam <srangana at 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).

Glusterfs 3.10.3 has been tagged. Packages for the various distributions will be available in a few days, and with that a more formal release announcement will be made. - Tagged code: https://github.com/gluster/glusterfs/tree/v3.10.3 - Release notes: https://github.com/gluster/glusterfs/blob/release-3.10/doc/release-notes/3.10.3.md Thanks, Raghavendra Talur NOTE: Tracker bug for 3.10.3 will be

Hi, It's time to prepare the 3.12.5 release, which falls on the 10th of each month, and hence would be 12-01-2018 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.12.5? 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)

On Fri, Nov 10, 2017 at 11:23:51AM +0530, Jiffin Tony Thottan wrote: > Hi, > > I am planning to do 3.12.3 release today 10:00 pm IST (4:30 pm GMT). > > Following bugs is removed from tracker list > > Bug 1501235 - [SNAPSHOT] Unable to mount a snapshot on client -- based on > discussion on gerrit, it can be target for 3.13 > instead of the 3.12.x release > > Bug

Hi, It's time to prepare the 3.12.4 release, which falls on the 10th of each month, and hence would be 12-12-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.12.4? 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)