Boost 1.58.0 has been released
Release 1.58.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains two new libraries and numerous enhancements and bug fixes for existing libraries. New Libraries * Endian: Types and conversion functions for correct byte ordering and more regardless of processor endianness. * Sort: Includes spreadsort, a general-case hybrid radix sort that is faster than O(n*log(n)) For details, including download links, see http://www.boost.org/users/news/version_1.58.0 You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.58.0/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes
On 04/17/2015 01:58 PM, Marshall Clow wrote:
Release 1.58.0 of the Boost C++ Libraries is now available.
<snip>
Thanks,
--The Boost release team
Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes
Thank you release team! -- Michael Caisse ciere consulting ciere.com
On April 17, 2015 7:56:07 PM EDT, Michael Caisse <mcaisse-lists@ciere.com> wrote:
On 04/17/2015 01:58 PM, Marshall Clow wrote:
Release 1.58.0 of the Boost C++ Libraries is now available.
<snip>
Thanks,
--The Boost release team
Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes
Thank you release team!
+1, especially this time out! ___ Rob (Sent from my portable computation engine)
On 18/04/2015 13:37, Rob Stewart wrote:
On April 17, 2015 7:56:07 PM EDT, Michael Caisse <mcaisse-lists@ciere.com> wrote:
On 04/17/2015 01:58 PM, Marshall Clow wrote:
Release 1.58.0 of the Boost C++ Libraries is now available.
<snip>
Thanks,
--The Boost release team
Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes
Thank you release team!
+1, especially this time out!
Thank you release team ! :)
2015-04-18 2:56 GMT+03:00 Michael Caisse <mcaisse-lists@ciere.com>:
On 04/17/2015 01:58 PM, Marshall Clow wrote:--The Boost release team
Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes
Thank you release team!
+1, well done! -- Best regards, Antony Polukhin
On Fri, Apr 17, 2015 at 3:58 PM, Marshall Clow <mclow.lists@gmail.com> wrote:
Release 1.58.0 of the Boost C++ Libraries is now available.
These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use.
This release contains two new libraries and numerous enhancements and bug fixes for existing libraries.
New Libraries * Endian: Types and conversion functions for correct byte ordering and more regardless of processor endianness. * Sort: Includes spreadsort, a general-case hybrid radix sort that is faster than O(n*log(n))
For details, including download links, see http://www.boost.org/users/news/version_1.58.0
You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.58.0/
To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html
Thanks,
--The Boost release team
Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes
The corresponding windows binaries for msvc-8.0 (SP1), msvc-9.0 (SP1), msvc-10.0 (SP1), msvc-11.0 (Update 4) and msvc-12.0 (Update 3) in 32 & 64 bit versions are now also available from sourceforge. https://sourceforge.net/projects/boost/files/boost-binaries/1.58.0/ Tom Kent
On 17 Apr 2015 at 21:58, Marshall Clow wrote:
For details, including download links, see http://www.boost.org/users/news/version_1.58.0
You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.58.0/
The automated script detected the release without human intervention for once, and 1.58 now appears at in a unified git repo suitable for CIs and git submoduling at: https://github.com/ned14/boost-release Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/
Daniel James created an entry point for 'convert' in the Boost 'develop' branch and 'convert' has been sitting there for quite some time. Now that Boost 1.58.0 has been released I would like to have 'convert' promoted from 'develop' to 'master' so that 'convert' would make it to 1.59. Is there anything that *I* can/need to do to have an entry point created for 'convert' in the Boost 'master' branch? Thank you, Vladimir.
Le 20/04/15 00:09, Vladimir Batov a écrit :
Daniel James created an entry point for 'convert' in the Boost 'develop' branch and 'convert' has been sitting there for quite some time. Now that Boost 1.58.0 has been released I would like to have 'convert' promoted from 'develop' to 'master' so that 'convert' would make it to 1.59. Is there anything that *I* can/need to do to have an entry point created for 'convert' in the Boost 'master' branch?
Hi, I would start a new thread and add you review manager. It is the review manager that should check everything is okay. Best Vicente
On 4/20/2015 1:10 PM, Vicente J. Botet Escriba wrote:
Le 20/04/15 00:09, Vladimir Batov a écrit :
Daniel James created an entry point for 'convert' in the Boost 'develop' branch and 'convert' has been sitting there for quite some time. Now that Boost 1.58.0 has been released I would like to have 'convert' promoted from 'develop' to 'master' so that 'convert' would make it to 1.59. Is there anything that *I* can/need to do to have an entry point created for 'convert' in the Boost 'master' branch?
Hi,
I would start a new thread and add you review manager. It is the review manager that should check everything is okay.
I was the review manager for 'convert' and it was accepted into Boost. It has been on 'develop' and been regression tested. I myself am not sure of the process of moving a library from 'develop' to 'master' so maybe someone dealing with the boostorg/boost project can comment. My educated guess is that it would involve a fork of boostorg/boost, a local 'pull --rebase' from that fork, changes locally that add the library submodule to 'master' with the necessary commit, a 'push' back to the fork, and then a pull request so that it shows up at boostorg/boost and eventually gets merged into the superproject. I believe part of the local changes are also that status/jamfile.v2 has to be changed so that the library's tests are added to it.
On 4/20/2015 1:10 PM, Vicente J. Botet Escriba wrote:
Le 20/04/15 00:09, Vladimir Batov a écrit :
Daniel James created an entry point for 'convert' in the Boost 'develop' branch and 'convert' has been sitting there for quite some time. Now that Boost 1.58.0 has been released I would like to have 'convert' promoted from 'develop' to 'master' so that 'convert' would make it to 1.59. Is there anything that *I* can/need to do to have an entry point created for 'convert' in the Boost 'master' branch?
Hi,
I would start a new thread and add you review manager. It is the review manager that should check everything is okay.
The review manager should have approved it before it was added to develop, release managers check that something is okay for release. I'll take it a look at it soon-ish if no one else does first (although it would be nice if someone else did). Give me a shout if I forget. On 20 April 2015 at 20:38, Edward Diener <eldiener@tropicsoft.com> wrote:
My educated guess is that it would involve a fork of boostorg/boost, a local 'pull --rebase' from that fork, changes locally that add the library submodule to 'master' with the necessary commit, a 'push' back to the fork, and then a pull request so that it shows up at boostorg/boost and eventually gets merged into the superproject. I believe part of the local changes are also that status/jamfile.v2 has to be changed so that the library's tests are added to it.
When I do it, I usually just copy the changes over. I don't know why you want to rebase.
Daniel, On 04/21/2015 10:04 AM, Daniel James wrote:
On 4/20/2015 1:10 PM, Vicente J. Botet Escriba wrote:
Le 20/04/15 00:09, Vladimir Batov a écrit :
Daniel James created an entry point for 'convert' in the Boost 'develop' branch and 'convert' has been sitting there for quite some time. Now that Boost 1.58.0 has been released I would like to have 'convert' promoted from 'develop' to 'master' so that 'convert' would make it to 1.59. Is there anything that *I* can/need to do to have an entry point created for 'convert' in the Boost 'master' branch?
Hi,
I would start a new thread and add you review manager. It is the review manager that should check everything is okay. The review manager should have approved it before it was added to develop, release managers check that something is okay for release.
I'll take it a look at it soon-ish if no one else does first (although it would be nice if someone else did). Give me a shout if I forget. ...
Thank you for your promptly reply. It's very much appreciated. If nothing happens, when you'd suggest I start "shouting"? A couple of weeks, perhaps? Just don't want to be interrupting prematurely/unnecessarily.
On 21 April 2015 at 02:13, Vladimir Batov <Vladimir.Batov@constrainttec.com> wrote:
Thank you for your promptly reply. It's very much appreciated. If nothing happens, when you'd suggest I start "shouting"? A couple of weeks, perhaps? Just don't want to be interrupting prematurely/unnecessarily.
Depends on how urgent it is, a week is generally appropriate, less if a deadline is coming up (that's in regard to releasing new libraries).
On 4/20/2015 8:04 PM, Daniel James wrote:
On 4/20/2015 1:10 PM, Vicente J. Botet Escriba wrote:
Le 20/04/15 00:09, Vladimir Batov a écrit :
Daniel James created an entry point for 'convert' in the Boost 'develop' branch and 'convert' has been sitting there for quite some time. Now that Boost 1.58.0 has been released I would like to have 'convert' promoted from 'develop' to 'master' so that 'convert' would make it to 1.59. Is there anything that *I* can/need to do to have an entry point created for 'convert' in the Boost 'master' branch?
Hi,
I would start a new thread and add you review manager. It is the review manager that should check everything is okay.
The review manager should have approved it before it was added to develop, release managers check that something is okay for release.
I'll take it a look at it soon-ish if no one else does first (although it would be nice if someone else did). Give me a shout if I forget.
On 20 April 2015 at 20:38, Edward Diener <eldiener@tropicsoft.com> wrote:
My educated guess is that it would involve a fork of boostorg/boost, a local 'pull --rebase' from that fork, changes locally that add the library submodule to 'master' with the necessary commit, a 'push' back to the fork, and then a pull request so that it shows up at boostorg/boost and eventually gets merged into the superproject. I believe part of the local changes are also that status/jamfile.v2 has to be changed so that the library's tests are added to it.
When I do it, I usually just copy the changes over. I don't know why you want to rebase.
What do you mean by "I usually just copy the changes over." ? Do you mean that you 'pull' from boostorg/boost, make the change locally and then push to the fork ?
When I do it, I usually just copy the changes over. I don't know why you want to rebase.
What do you mean by "I usually just copy the changes over." ?
Do you mean that you 'pull' from boostorg/boost, make the change locally and then push to the fork ?
Pretty much, although I don't use 'pull', I typically just create a branch directly from the remote branch. If you want to know my exact procedure, I use the github command line utility to create and update the fork, it's something like: hub fork git fetch origin git checkout origin/develop -b branch-name # If necessary: git submodule update --init git push -u danieljames # Commit changes. git push If it isn't clear, 'origin' is the boostorg repository, 'hub fork' creates a remote with your username (in my case danieljames). 'git push -u' is important as it sets the branch to push to my account. I usually use the web interface to create the pull request.
On 19 April 2015 at 23:09, Vladimir Batov <Vladimir.Batov@constrainttec.com> wrote:
Daniel James created an entry point for 'convert' in the Boost 'develop' branch and 'convert' has been sitting there for quite some time. Now that Boost 1.58.0 has been released I would like to have 'convert' promoted from 'develop' to 'master' so that 'convert' would make it to 1.59. Is there anything that *I* can/need to do to have an entry point created for 'convert' in the Boost 'master' branch?
I was just checking the library to see if it's ready for master, we generally like to have a mostly clean inspect report before adding it. You can see current issues at: http://boost.cowic.de/rc/docs-inspect-develop.html#convert Although that's a few weeks out of date, I'll run a new documentation build tomorrow, which should update it. If you don't know about handling min and max macros, that's documented at: http://www.boost.org/development/requirements.html#Design_and_Programming Can you also have another look at the test results? Particularly the gcc 5 errors, which I think is released now. Although I suppose it's 5.1 that matters. For other failures, if they're not fixable, they should be marked up in status/explicit-failures-markup.xml if possible, it's pretty limited though, so it might not be.
participants (13)
-
Antony Polukhin -
Damien Buhl -
Daniel James -
Edward Diener -
Ion Gaztañaga -
Marshall Clow -
Michael Caisse -
Niall Douglas -
Rob Stewart -
Sergey Shandar -
Tom Kent -
Vicente J. Botet Escriba -
Vladimir Batov