Subject: Re: [boost] Reminder: Boost Master branch will close for the 1.65.0 release on Wednesday
From: Daniel James (dnljms_at_[hidden])
Date: 2017-08-01 19:14:51
On 1 August 2017 at 19:27, Stefan Seefeld via Boost
> On 01.08.2017 05:12, Daniel James via Boost wrote:
>> I can see other problems with a more distributed approach. We'd lose
>> the ability to edit release notes, which we do on occasion, and pull
>> requests also make it easier to track changes as someone has to
>> approve them.
> Why would anyone want to edit or even just approve release notes I wrote
> about a project I maintain ?
Fix links, typos, markup etc. A lot of that is done by Akira Takahashi.
>> It wouldn't be clear which module branch to use, master
>> seems the obvious choice, but it couldn't be used when master is
>> frozen. And changes to the release notes after a release could also be
>> It would also require everyone to write their own release notes.
> Yes indeed. So what ? Who is writing them now ?
The answer immediately follows.
>> Sometimes people email me if they don't want to write quickbook markup
> All this sounds like another case of someone being afraid of loosing
> control. With 100+ libraries being hosted by the Boost organization, I
> think it's time to come to terms with the idea that there is no way to
> control them top-down.
Don't be silly, I wrote a lot of the scripts that allow library
maintainers to manage things themselves. Why on Earth would I so
concerned about controlling the release notes? What's so important
about them? I'm getting tired of people casting aspersions on anyone
who disagrees with them.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk