Re: [boost] [1.38.0] branches/release frozen

Subject: Re: [boost] [1.38.0] branches/release frozen
From: David Abrahams (dave_at_[hidden])
Date: 2009-02-07 22:49:30

on Sat Feb 07 2009, Daniel James <daniel_james-AT-fmail.co.uk> wrote:

> 2009/2/7 Andrey Semashev <andrey.semashev_at_[hidden]>:
>>
>> As a side note, some projects out there employ dual change list. The one
>> that goes into the News page enlists only major changes and a link to the
>> second one with more detailed description. The latter one is often compiled
>> from particular tickets that were solved in this release.
>>
>> I'm not suggesting to do the same in this release, but this looks like a
>> good practice to follow in future to me.
>
> It's a good idea, but we don't tend to create tickets for every issue.

We should, though.

> So this couldn't be done automatically from the tickets at the moment.
> We also have a culture of being very flexible about how libraries are
> maintained, these things are largely up to the library maintainers.
> Understandably, this often frustrates users who'd like a bit more
> consistency.

Yup.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com