Re: [boost] Fwd: Boost.Python build error in 1.58 RC1, 2 and 3 (OK in Beta 1)

Subject: Re: [boost] Fwd: Boost.Python build error in 1.58 RC1, 2 and 3 (OK in Beta 1)
From: Olaf van der Spek (ml_at_[hidden])
Date: 2015-04-10 08:40:30

On Thu, Apr 9, 2015 at 5:40 PM, Beman Dawes <bdawes_at_[hidden]> wrote:
> On Thu, Apr 9, 2015 at 10:01 AM, Olaf van der Spek <ml_at_[hidden]> wrote:
>
>> On Thu, Apr 9, 2015 at 3:51 PM, Marshall Clow <mclow.lists_at_[hidden]>
>> wrote:
>> > PLEASE STOP COMMITTING DIRECTLY TO MASTER!
>> >
>> > That's not how we do development on Boost.
>> >
>> > Commit your changes to the develop branch, give the testers a chance to
>> > run, and *then*, if everything seems OK, merge from develop to master.
>>
>> Can't this be handled by code / permissions?
>>
>
> Could you explain what you mean by "handled by code / permissions"?
>
> While I understand how a continuous integration framework might only merge
> to master when develop tests are passing satisfactorily, I'm not aware of
> any way to prevent breaking merges with our current testing approach.

Is it not possible to only allow merges from develop into master?

-- 
Olaf