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 ? -- Regards, Jiffin ----- Original Message ----- From: "Shyam Ranganathan" <[email protected]> To: [email protected], [email protected], [email protected] 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, [email protected] 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? https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-12-dashboard 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 > [email protected] > http://lists.gluster.org/mailman/listinfo/maintainers > _______________________________________________ maintainers mailing list [email protected] http://lists.gluster.org/mailman/listinfo/maintainers _______________________________________________ packaging mailing list [email protected] http://lists.gluster.org/mailman/listinfo/packaging
