Re: [boost] [release] 1.63.0 now closed for new libraries and breaking changes

Subject: Re: [boost] [release] 1.63.0 now closed for new libraries and breaking changes
From: Daniel James (dnljms_at_[hidden])
Date: 2016-10-27 04:42:31

On 27 October 2016 at 07:10, Oliver Kowalke <oliver.kowalke_at_[hidden]> wrote:
> Hello Daniel,
> is boost-1.63 a bugfix release or will boost released monthly?
> Oliver

No, there's a shorter release cycle because the last release was late.
If you look on the calendar, it's just under two and a half months
from the release of 1.62.0 to the scheduled release of 1.63.0. It's
not much shorter than the traditional three months. There's still
another week for major changes, and if there's something important you
want to merge and you didn't realise the deadline was coming up, we
can be a little flexible, especially if other libraries don't depend
on yours.

Looking at your release notes, your breaking change is that you want
to do is rename some classes. Then it's probably best to do it in a
non-breaking manner anyway, and deprecate the old name for later
removal. Since your library requires C++11, you might be able to use a
template alias? I'm not sure how widely they're supported.