[Gluster-Maintainers] Release 3.11.1: Scheduled for 20th of June
atumball at redhat.com
Tue Jun 20 10:13:38 UTC 2017
On Mon, Jun 19, 2017 at 11:01 PM, Shyam <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 
> - Tests of concern are:
> - ./tests/basic/afr/add-brick-self-heal.t 
> @pranith, this seems to be failing more often now, do we know why or
> any pointers?
> - ./tests/encryption/crypt.t 
> @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
> 2) Pending review queue:  (@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
Please consider https://review.gluster.org/#/c/17569/ and
This is requested from Kubernetes integration.
> "Releases are made better together"
>  All regression failures for 3.11.1 : https://fstat.gluster.org/summ
>  add-brick-self-heal.t failures: https://fstat.gluster.org/fail
>  crypt.t failure(s) on all branches: https://fstat.gluster.org/fail
>  Pending reviews needing attention: https://review.gluster.org/#/q
> On 06/06/2017 09:24 AM, Shyam wrote:
>> It's time to prepare the 3.11.1 release, which falls on the 20th of
>> each month , 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  as blockers
>> for the release, or at the very least post them as a response to this
>> 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  to check on the status of your patches to 3.11 and get
>> these going
>> 3) Empty release notes are posted here , 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
>>  Release bug tracker:
>>  3.11 review dashboard:
>>  Release notes WIP: https://review.gluster.org/17480
>>  Release calendar: https://www.gluster.org/community/release-schedule/
> maintainers mailing list
> maintainers at gluster.org
Amar Tumballi (amarts)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the maintainers