[release] 1.76.0 open for merging

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[release] 1.76.0 open for merging

Boost - Dev mailing list
The master branch is open for merging all stable changes from develop, including bug fixes and major upgrades to existing libraries. Breaking changes should be coordinated via the mailing list with the developers of the other libraries affected. New libraries may be added, but require permission of a release manager.

In other words, merging does not require permission from a release manager, except for new libraries.

Boost Calendar with the release schedule: http://www.boost.org/development/index.html <http://www.boost.org/development/index.html>

Release schedule explanation: https://github.com/boostorg/wiki/wiki/Releases%3A-Schedule <https://github.com/boostorg/wiki/wiki/Releases%3A-Schedule>

Release practices for developers: http://svn.boost.org/trac/boost/wiki/ImprovingPractices <http://svn.boost.org/trac/boost/wiki/ImprovingPractices>

-- The Boost Release Team


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] 1.76.0 open for merging

Boost - Dev mailing list
On 11/12/2020 20:14, Marshall Clow via Boost wrote:

> The master branch is open for merging all stable changes from develop, including bug fixes and major upgrades to existing libraries. Breaking changes should be coordinated via the mailing list with the developers of the other libraries affected. New libraries may be added, but require permission of a release manager.

A reminder to all that after a year and three releases of warning,
Outcome v2.2, which breaks all Outcome v2.1 based code, is just about to
be merged.

Niall

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost