On Thursday 11 January 2018 12:24 PM, Hans Henrik Happe wrote:
Hi,
I wonder how this procedure works. I could add a bug that I think is a
*blocker*, but there might not be consensus.
You can add it the tracker bug. Depending on the severity we may or may
not take it for 3.12.5
--
Jiffin
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,
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) Pending reviews in the 3.12 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.12 and get
these going
3) I have made checks on what went into 3.10 post 3.12 release and if
these fixes are already included in 3.12 branch, then status on this is
*green*
as all fixes ported to 3.10, are ported to 3.12 as well.
Thanks,
Jiffin
[1] Release bug tracker:
https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.12.5
[2] 3.12 review dashboard:
https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-12-dashboard
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
