[Gluster-Maintainers] glusterfs-3.12.7 released
srangana at redhat.com
Tue Mar 20 18:48:06 UTC 2018
On 03/20/2018 01:10 PM, Jiffin Thottan wrote:
> Hi Shyam,
> Actually I planned to do the release on March 8th(posted the release note on that day). But it didn't happen.
> I didn't merge any patches post sending the release note(blocker bug had some merge conflict issue on that so I skipped AFAIR).
> I performed 3.12.7 tagging yesterday and ran the build job today.
> Can u please provide a suggestion here ? Do I need to perform a 3.12.7-1 for the blocker bug ?
I see that the bug is marked against the tracker, but is not a
regression or an issue that is serious enough that it cannot wait for
the next minor release.
Copied Atin to the mail, who opened that issue for his comments. If he
agrees, let's get this moving and get the fix into the next minor release.
> ----- Original Message -----
> From: "Shyam Ranganathan" <srangana at redhat.com>
> To: jenkins at build.gluster.org, packaging at gluster.org, maintainers at gluster.org
> Sent: Tuesday, March 20, 2018 9:06:57 PM
> Subject: Re: [Gluster-Maintainers] glusterfs-3.12.7 released
> On 03/20/2018 11:19 AM, jenkins at build.gluster.org wrote:
>> SRC: https://build.gluster.org/job/release-new/47/artifact/glusterfs-3.12.7.tar.gz
>> HASH: https://build.gluster.org/job/release-new/47/artifact/glusterfs-3.12.7.sha512sum
>> This release is made off jenkins-release-47
> Jiffin, there are about 6 patches ready in the 3.12 queue, that are not
> merged for this release, why?
> The tracker bug for 3.12.7 calls out
> https://bugzilla.redhat.com/show_bug.cgi?id=1543708 as a blocker, and
> has a patch, which is not merged.
> Was this some test packaging job?
>> maintainers mailing list
>> maintainers at gluster.org
> maintainers mailing list
> maintainers at gluster.org
More information about the maintainers