[Gluster-devel] [Gluster-Maintainers] Release 3.11.1: Scheduled for 20th of June

Shyam srangana at redhat.com
Tue Jun 20 14:04:45 UTC 2017


On 06/20/2017 06:13 AM, Amar Tumballi wrote:
>
>
> On Mon, Jun 19, 2017 at 11:01 PM, Shyam <srangana at redhat.com
> <mailto:srangana at redhat.com>> wrote:
>
>     3.11.1 Release tagging is tomorrow (20th June, 2017).
>
>     Here are some key things to do before we tag the release,
>
>     1) Regression failures: (@pranith, @maintainers)
>       - Overall regression failures status on 3.11 since .0 release can
>     be seen here [1]
>       - Tests of concern are:
>         - ./tests/basic/afr/add-brick-self-heal.t [2]
>           @pranith, this seems to be failing more often now, do we know
>     why or any pointers?
>
>         - ./tests/encryption/crypt.t [3]
>           @maintainers? This seems to have a higher incident of failures
>     recently on master (and just one instance on 3.11 branch). All are
>     cores, so possibly some other change is causing this. Any updates
>     from anyone on this?
>
>     2) Pending review queue: [4] (@poornima, @csaba, @soumya, @ravishankar)
>       - There are some reviews that do not have CentOS (or NetBSD) votes
>     yet, and are present to be committed for over a week, I have kicked
>     off rechecks as appropriate for some. Patch owners please keep a
>     watch out for the same.
>
>     3) Backport status: (IOW, things backported to older released
>     branches should be present in the later ones (in this case ported to
>     3.8/3.10 to be present in 3.11))
>       - This is clean as of today, pending merge of
>     https://review.gluster.org/17512 <https://review.gluster.org/17512>
>
>
> Please consider https://review.gluster.org/#/c/17569/ and
> https://review.gluster.org/#/c/17573/
>
> This is requested from Kubernetes integration.

These are merged now. Considering this is an STM release I am taking in 
the feature into a minor release.

Request you or Csaba post a release note as a comment @ 
https://review.gluster.org/#/c/17480/

>
> Thanks.
> Amar
>
>
>     Thanks,
>     Shyam
>
>     "Releases are made better together"
>
>     [1] All regression failures for 3.11.1 :
>     https://fstat.gluster.org/summary?start_date=2017-06-01&end_date=2017-06-20&branch=release-3.11
>     <https://fstat.gluster.org/summary?start_date=2017-06-01&end_date=2017-06-20&branch=release-3.11>
>
>     [2] add-brick-self-heal.t failures:
>     https://fstat.gluster.org/failure/2?start_date=2017-06-01&end_date=2017-06-20&branch=release-3.11
>     <https://fstat.gluster.org/failure/2?start_date=2017-06-01&end_date=2017-06-20&branch=release-3.11>
>
>     [3] crypt.t failure(s) on all branches:
>     https://fstat.gluster.org/failure/62?start_date=2017-06-01&end_date=2017-06-20&branch=all
>     <https://fstat.gluster.org/failure/62?start_date=2017-06-01&end_date=2017-06-20&branch=all>
>
>     [4] Pending reviews needing attention:
>     https://review.gluster.org/#/q/status:open+starredby:srangana%2540redhat.com
>     <https://review.gluster.org/#/q/status:open+starredby:srangana%2540redhat.com>
>
>
>     On 06/06/2017 09:24 AM, Shyam 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 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.11 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.11 and get
>         these going
>
>         3) Empty release notes are posted here [3], if there are any
>         specific
>         call outs for 3.11 beyond bugs, please update the review, or leave a
>         comment in the review, for us to pick it up
>
>         Thanks,
>         Shyam/Kaushal
>
>         [1] Release bug tracker:
>         https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.11.1
>         <https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.11.1>
>
>         [2] 3.11 review dashboard:
>         https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-11-dashboard
>         <https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-11-dashboard>
>
>
>         [3] Release notes WIP: https://review.gluster.org/17480
>         <https://review.gluster.org/17480>
>
>         [4] Release calendar:
>         https://www.gluster.org/community/release-schedule/
>         <https://www.gluster.org/community/release-schedule/>
>
>     _______________________________________________
>     maintainers mailing list
>     maintainers at gluster.org <mailto:maintainers at gluster.org>
>     http://lists.gluster.org/mailman/listinfo/maintainers
>     <http://lists.gluster.org/mailman/listinfo/maintainers>
>
>
>
>
> --
> Amar Tumballi (amarts)


More information about the Gluster-devel mailing list