Re: [Boost-users] [boost] Boost 1_59_0_b1_rc1 is available for testing

Subject: Re: [Boost-users] [boost] Boost 1_59_0_b1_rc1 is available for testing
From: Michael (mwpowellhtx_at_[hidden])
Date: 2015-07-15 06:25:52

On July 15, 2015 12:20:40 AM EDT, Gavin Lambert <gavinl_at_[hidden]> wrote:
>On 15/07/2015 14:59, Edward Diener wrote:
>> Because MPL is so central to everything it seems it is too late to
>get
>> these fixes into 'master', have the regression tested on 'master' and
>> into the upcoming release at this point.
>
>Take this with a grain of salt, since I'm not a library maintainer or 
>release manager, but:

Personally I get put off by making excuses. Take care of it, just get 'er done. This isn't the first time, but it can be the last. Just have to want to expect excellence.

>Since it's still at a beta release stage (if I'm understanding 
>correctly), this seems to me like the perfect time to merge bugfixes, 
>especially ones that have already been tested on develop.
>
>Part of the point of having a beta cycle is to discover these 
>accidentally-left-out elements and correct them.
>
>In my view it's far better to delay the release slightly (if that would
>
>even happen in this case, which it might not) than to ship with known 
>bugs for which fixes are already committed.  (When fixes are yet to be 
>developed, it's a different story, of course.)
>
>Again, this view might change a little if the fixes are breaking 
>changes, but I presume this is not the case since they're tested on 
>develop.  Or it just means a few more fixes might need to be merged as
>well.
>
>
>_______________________________________________
>Boost-users mailing list
>Boost-users_at_[hidden]
>http://lists.boost.org/mailman/listinfo.cgi/boost-users

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.