On 23 May 2014 11:29, Andrzej Krzemienski wrote:

2014-05-23 10:45 GMT+02:00 Daniel James :

...

...

Is there a timeframe for the release of Boost 1.56? The current 1.56

On 22 May 2014 19:55, Jonathan Jones wrote: page simply states that it's at an early stage in its release cycle (but it has said this for months).

...

http://www.boost.org/users/history/version_1_56_0.html

Fixed. Hopefully it's clearer now.

How can I add the list of changes in Boost.Optional to this page? Regards, &rzej

You can create a pull request using github, click the 'edit' button at the top of this page: https://github.com/boostorg/website/blob/master/feed/history/boost_1_56_0.qb... Or you can just mail me if you prefer.

On 23 May 2014 12:10, John Maddock wrote:

...

...

Is there a timeframe for the release of Boost 1.56? The current 1.56 page simply states that it's at an early stage in its release cycle (but it has said this for months).

http://www.boost.org/users/history/version_1_56_0.html

Fixed. Hopefully it's clearer now.

I still don't see a release schedule on the calendar - do we have one yet?

If we had one, it would be on the calendar.

On May 23, 2014, at 4:49 AM, Beman Dawes wrote:

On Fri, May 23, 2014 at 7:10 AM, John Maddock wrote:

...

Is there a timeframe for the release of Boost 1.56? The current 1.56 page

...

...

simply states that it's at an early stage in its release cycle (but it has said this for months).

http://www.boost.org/users/history/version_1_56_0.html

Fixed. Hopefully it's clearer now.

I still don't see a release schedule on the calendar - do we have one yet?

Yes. Discussed and decided in Aspen. We are going to pick up the regular schedule. I assume that means the next release will be scheduled for the first Monday in August, but Marshall will be verifying that.

Several other important decisions were made last week at various C++Now meetings, but haven't been posted to the list yet. Beyond the usual catch up after being out-of-the-office for a week, today is the deadline for papers for the upcoming C++ standards committee meeting, and most of the Boost people involved are in ship mode trying to finish committee papers.

Here’s my proposal for release (based on looking at the 1.53 schedule, with some extra time inserted): June 16: Master closed for new libraries and breaking changes June 30: Master closed, except by permission July 7: 1.56.0 rc1 July 8: Master open for bug fixes and doc changes July 21: Master closed, except by permission July 28: 1.56.0 rc2 August 4: 1.56.0 release — Marshall

2014-05-23 11:45 GMT+02:00 Andrey Semashev :

...

Hi folks,

Is there a timeframe for the release of Boost 1.56? The current 1.56

On Thursday 22 May 2014 18:55:24 Jonathan Jones wrote: page

...

simply states that it's at an early stage in its release cycle (but it has said this for months).

http://www.boost.org/users/history/version_1_56_0.html

I'm asking in the context of Visual Studio 2013. Boost 1.55 is known to have issues with VS2013, which I'm hoping the 1.56 release would address.

+1

I'd like to know the current state of the release. What's left to be done? Any blockers? Is there anything I can do to help it?

It's starting to feel like the old days circa 1.34, I wouldn't like to see that happen again. If there is no Boost release in the forseeable future, should the library authors initiate their library independent releases?

From reading the instructions for Modular Boost maintenance ( https://svn.boost.org/trac/boost/wiki/StartModMaint) I gathered that it is already an encouraged practice. A commit in branch master is to be treated as the new release of your library -- and you can do it whenever you like, and use your own numbering convention.

Regards, &rzej