Hi,
It's time to prepare the 3.10.1 release, which falls on the 30th of each
month, and hence would be Mar-30th-2017 this time around.
We have one blocker issue for the release, which is [1] "auth failure
after upgrade to GlusterFS 3.10", that we are tracking using the release
tracker bug [2]. @Atin, can we have this fixed in a day or 2, or does it
look like we may slip beyond that?
This mail is to call out the following,
1) Are there any pending *blocker* bugs that need to be tracked for
3.10.1? If so mark them against the provided tracker [2] as blockers for
the release, or at the very least post them as a response to this mail
2) Pending reviews in the 3.10 dashboard will be part of the release,
*iff* they pass regressions and have the review votes, so use the
dashboard [3] to check on the status of your patches to 3.10 and get
these going
3) I have made checks on what went into 3.8 post 3.10 release and if
these fixes are included in 3.10 branch, the status on this is *green*
as all fixes ported to 3.8, are ported to 3.10 as well
4) First cut of the release notes are posted here [4], if there are any
specific call outs for 3.10 beyond bugs, please update the review, or
leave a comment in the review, for me to pick it up
Thanks,
Shyam
[1] Pending blocker bug for 3.10.1:
https://bugzilla.redhat.com/show_bug.cgi?id=1429117
[2] Release bug tracker:
https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.10.1
[3] 3.10 review dashboard:
https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-10-dashboard
[4] Release notes WIP: https://review.gluster.org/16957
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
