[Gluster-devel] [Gluster-Maintainers] Release 5: Master branch health report (Week of 30th July)
sankarshan.mukhopadhyay at gmail.com
Mon Aug 6 00:39:51 UTC 2018
On Mon, Aug 6, 2018 at 5:17 AM, Amye Scavarda <amye at redhat.com> wrote:
> On Sun, Aug 5, 2018 at 3:24 PM Shyam Ranganathan <srangana at redhat.com>
>> On 07/31/2018 07:16 AM, Shyam Ranganathan wrote:
>> > On 07/30/2018 03:21 PM, Shyam Ranganathan wrote:
>> >> On 07/24/2018 03:12 PM, Shyam Ranganathan wrote:
>> >>> 1) master branch health checks (weekly, till branching)
>> >>> - Expect every Monday a status update on various tests runs
>> >> See https://build.gluster.org/job/nightly-master/ for a report on
>> >> various nightly and periodic jobs on master.
>> > Thinking aloud, we may have to stop merges to master to get these test
>> > failures addressed at the earliest and to continue maintaining them
>> > GREEN for the health of the branch.
>> > I would give the above a week, before we lockdown the branch to fix the
>> > failures.
>> > Let's try and get line-coverage and nightly regression tests addressed
>> > this week (leaving mux-regression open), and if addressed not lock the
>> > branch down.
>> Health on master as of the last nightly run  is still the same.
>> Potential patches that rectify the situation (as in ) are bunched in
>> a patch  that Atin and myself have put through several regressions
>> (mux, normal and line coverage) and these have also not passed.
>> Till we rectify the situation we are locking down master branch commit
>> rights to the following people, Amar, Atin, Shyam, Vijay.
>> The intention is to stabilize master and not add more patches that my
>> destabilize it.
>> Test cases that are tracked as failures and need action are present here
>> @Nigel, request you to apply the commit rights change as you see this
>> mail and let the list know regarding the same as well.
>>  Patches that address regression failures:
>>  Bunched up patch against which regressions were run:
>>  Failing tests list:
>>  Nightly run dashboard: https://build.gluster.org/job/nightly-master/
> Locking master is fine, this seems like there's been ample notice and
> Do we have test criteria to indicate when we're unlocking master? X amount
> of tests passing, Y amount of bugs?
The "till we rectify" might just include 3 days of the entire set of
tests passing - thinking out loud here.
More information about the Gluster-devel