From: Loic Dachary <loic@dachary.org>
To: Sage Weil <sage@newdream.net>, ceph-devel@vger.kernel.org
Subject: Re: master branch merges must pass unit tests
Date: Wed, 9 Nov 2016 10:29:38 +0100 [thread overview]
Message-ID: <5822EC82.6080306@dachary.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1611082331480.29278@piezo.us.to>
On 09/11/2016 00:34, Sage Weil wrote:
> On Tue, 8 Nov 2016, Sage Weil wrote:
>> I enabled the github check that the unit tests pass in order to merge to
>> master. These tests still aren't completely reliable, but they're close,
>> and we'll make better progress if we start enforcing it now.
>
> I went a bit further and also checked the box requiring a review and
> preventing pushes directly to master branch. These are already uneforced
> requirements so this shouldn't slow people down *except* that we need to
> start using the new github 'review' feature that lets you explicitly
> approve changes.
>
> Again, the core developers can override these restrictions if necessary.
>
> I haven't done anything to the stable branches, but we might want to do
> the same thing there...
Good move :-) I will do the same for the stable branches.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
next prev parent reply other threads:[~2016-11-09 9:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 21:49 master branch merges must pass unit tests Sage Weil
2016-11-08 21:56 ` Patrick Donnelly
2016-11-08 22:01 ` Ken Dreyer
2016-11-08 23:34 ` Sage Weil
2016-11-09 9:29 ` Loic Dachary [this message]
2016-11-09 11:32 ` Igor Fedotov
2016-11-09 14:19 ` Sage Weil
2016-11-11 2:14 ` Patrick Donnelly
2016-11-11 2:48 ` Patrick Donnelly
2016-11-09 13:37 ` Alfredo Deza
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5822EC82.6080306@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.