Subject: Re: [boost] Reminder: Boost Master branch will close for the 1.65.0 release on Wednesday
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2017-08-01 20:18:42
On 01.08.2017 15:21, Andrey Semashev via Boost wrote:
> On 08/01/17 22:14, Daniel James via Boost wrote:
>> On 1 August 2017 at 19:27, Stefan Seefeld via Boost
>> <boost_at_[hidden]> wrote:
>>> 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
>>> about a project I maintain ?
>> Fix links, typos, markup etc. A lot of that is done by Akira Takahashi.
> Multiple times we also had to add to release notes after the release
> has been shipped. For example, add notes about critical problems and
> links to patches.
Yes, all of which can be done per project, if Boost would allow release
notes to be stored in the project-specific repositories, and rendered
from project-specific documentation, rather than all from a single
-- ...ich hab' noch einen Koffer in Berlin...
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk