Boost 1.61.0 Release Candidate 1

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

Boost 1.61.0 Release Candidate 1

Vladimir Prus-4

The release candidates for the 1.61.0 release are now available at:

     http://boost.cowic.de/rc/boost_1_61_0_rc1.zip
     http://boost.cowic.de/rc/boost_1_61_0_rc1.7z
     http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.bz2
     http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz

The SHA256 checksums are as follows:

     dcd11a91a412b2e8a78678b38cb2a74857e61f9bfe2577de9fd70be770100d54  boost_1_61_0_rc1.7z
     476937369c7a82103b734ccae85d35a523cdb7f8462c5f2fe1217ff0c8e2a7df  boost_1_61_0_rc1.tar.bz2
     e60dee39ebb29d24bf8a4ef9aec34dbb8c1b9b219d4737ea4b358f38b1aab2b7  boost_1_61_0_rc1.tar.gz
     e5f662f44a65c5c19450b8a1c07f75c7d5f16e58667871e856ba3984ec082006  boost_1_61_0_rc1.zip

As always, the release managers would appreciate it if you download
the candidate of your choice and give building it a try. Please report
both success and failure, and anything else that is noteworthy.

The signed list of checksums is also attached, signed with the following key:

     https://pgp.mit.edu/pks/lookup?op=get&search=0xDA472E8659753BA4
     Key fingerprint C5F0 F367 AA66 616F B839  806E DA47 2E86 5975 3BA4


Thanks!

-- The release managers


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

boost_1_61_0_rc1.sums.asc (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [EXTERNAL] Boost 1.61.0 Release Candidate 1

Belcourt, Kenneth
> On Apr 27, 2016, at 3:37 PM, Vladimir Prus <[hidden email]> wrote:
>
> The release candidates for the 1.61.0 release are now available at:
>
>    http://boost.cowic.de/rc/boost_1_61_0_rc1.zip
>    http://boost.cowic.de/rc/boost_1_61_0_rc1.7z
>    http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.bz2
>    http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz
>
> As always, the release managers would appreciate it if you download
> the candidate of your choice and give building it a try. Please report
> both success and failure, and anything else that is noteworthy.

Built and ran all status/Jamfile.v2 tests from [graph ... MPI] inclusive, with clang on El Capitan.  No obvious issues though there are many test failures in hana and at least one failure in integer, io, iostreams, iterator, lexical_cast, locale, and lockfree.  There’re  a fair number of warnings.  Checked that various documentation links for the new, and some existing, libraries worked fine.

—- Noel


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

Re: [EXTERNAL] Boost 1.61.0 Release Candidate 1

Vladimir Prus-4
On 4/28/2016 5:29 AM, Belcourt, Kenneth wrote:

>> On Apr 27, 2016, at 3:37 PM, Vladimir Prus <[hidden email]> wrote:
>>
>> The release candidates for the 1.61.0 release are now available at:
>>
>>    http://boost.cowic.de/rc/boost_1_61_0_rc1.zip
>>    http://boost.cowic.de/rc/boost_1_61_0_rc1.7z
>>    http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.bz2
>>    http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz
>>
>> As always, the release managers would appreciate it if you download
>> the candidate of your choice and give building it a try. Please report
>> both success and failure, and anything else that is noteworthy.
>
> Built and ran all status/Jamfile.v2 tests from [graph ... MPI] inclusive, with clang on El Capitan.  No obvious issues though
 >  there are many test failures in hana and at least one failure in integer, io, iostreams, iterator,
 > lexical_cast, locale, and lockfree.
 >
> There’re  a fair number of warnings.  Checked that various documentation links for the new, and some existing, libraries worked fine.

Thanks for testing! I've done builds on Windows and OSX, and everything appear to build, although I'd say the number
of warnings is rather disappointing - seem that some libraries trigger warnings in MPL.

Hana is failing across the board - it only passes with 4 toolsets in the matrix (clang-linuxg 3.6 and 3.7, gcc 6.0.1 and
7.0) - it would be nice it expected failures markup were up-to-date.

--
Vladimir Prus
http://vladimirprus.com


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

Re: Boost 1.61.0 Release Candidate 1

Rob Stewart-2
In reply to this post by Vladimir Prus-4
On April 27, 2016 5:37:32 PM EDT, Vladimir Prus <[hidden email]> wrote:
>
>The release candidates for the 1.61.0 release are now available

Thanks for your work to create this release, especially given the last minute breakages, etc.

___
Rob

(Sent from my portable computation engine)

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

Re: Boost 1.61.0 Release Candidate 1

Tom Kent
In reply to this post by Vladimir Prus-4
On Wed, Apr 27, 2016 at 4:37 PM, Vladimir Prus <[hidden email]>
wrote:

>
> The release candidates for the 1.61.0 release are now available at:
>
>     http://boost.cowic.de/rc/boost_1_61_0_rc1.zip
>     http://boost.cowic.de/rc/boost_1_61_0_rc1.7z
>     http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.bz2
>     http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz
>
> The SHA256 checksums are as follows:
>
>     dcd11a91a412b2e8a78678b38cb2a74857e61f9bfe2577de9fd70be770100d54
> boost_1_61_0_rc1.7z
>     476937369c7a82103b734ccae85d35a523cdb7f8462c5f2fe1217ff0c8e2a7df
> boost_1_61_0_rc1.tar.bz2
>     e60dee39ebb29d24bf8a4ef9aec34dbb8c1b9b219d4737ea4b358f38b1aab2b7
> boost_1_61_0_rc1.tar.gz
>     e5f662f44a65c5c19450b8a1c07f75c7d5f16e58667871e856ba3984ec082006
> boost_1_61_0_rc1.zip
>
> As always, the release managers would appreciate it if you download
> the candidate of your choice and give building it a try. Please report
> both success and failure, and anything else that is noteworthy.


Builds on windows/visual studio look good:

toolset     arch    compile Link    Execute
msvc-8.0    32      X       X       X
msvc-8.0    64      X       X       X
msvc-9.0    32      X       X       X
msvc-9.0    64      X       X       X
msvc-10.0   32      X       X       X
msvc-10.0   64      X       X       X
msvc-11.0   32      X       X       X
msvc-11.0   64      X       X       X
msvc-12.0   32      X       X       X
msvc-12.0   64      X       X       X
msvc-14.0   32      X       X       X
msvc-14.0   64      X       X       X

Compile means that the b2 command completed without errors
Install means that the installers for the respective version were generated
Link means that visual studio was able to link a sample executable to a
library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated
Execute means that the linked program executed without errors.

Logs are here:

32-bit: https://gist.github.com/teeks99/5456835f5e86bfa6498ee4b6d8acf5e3
64-bit: https://gist.github.com/teeks99/3d2bd9ac7eef099aeaa52991a3f5b74f

Tom

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

Re: [EXTERNAL] Boost 1.61.0 Release Candidate 1

Louis Dionne
In reply to this post by Vladimir Prus-4
Vladimir Prus <vladimir.prus <at> gmail.com> writes:

>
> [...]
>
> Hana is failing across the board - it only passes with 4 toolsets in the
> matrix (clang-linuxg 3.6 and 3.7, gcc 6.0.1 and 7.0) - it would be nice it
> expected failures markup were up-to-date.

I tried marking some toolsets as "unusable" in a PR [1] a while ago, but it
seems like that didn't work. What am I missing? I would like to rectify the
situation, as the current matrix for Hana is not very useful.

Regards,
Louis

[1]: https://github.com/boostorg/boost/pull/111



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

Re: [EXTERNAL] Boost 1.61.0 Release Candidate 1

Belcourt, Kenneth
In reply to this post by Rob Stewart-2

> On Apr 28, 2016, at 2:41 AM, Rob Stewart <[hidden email]> wrote:
>
> On April 27, 2016 5:37:32 PM EDT, Vladimir Prus <[hidden email]> wrote:
>>
>> The release candidates for the 1.61.0 release are now available
>
> Thanks for your work to create this release, especially given the last minute breakages, etc.

+1


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

Re: [EXTERNAL] Boost 1.61.0 Release Candidate 1

Thomas Trummer-2
In reply to this post by Vladimir Prus-4

> On 28 Apr 2016, at 08:48, Vladimir Prus <[hidden email]> wrote:
>
> Hana is failing across the board - it only passes with 4 toolsets in the matrix (clang-linuxg 3.6 and 3.7, gcc 6.0.1 and 7.0) - it would be nice it expected failures markup were up-to-date.

Similarly Boost.Compute should probably check for the existence of <CL/cl.h> before running tests if possible.

Thomas

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

Re: Boost 1.61.0 Release Candidate 1

Vladimir Prus-4
In reply to this post by Rob Stewart-2
On 28.04.2016 11:41, Rob Stewart wrote:
> On April 27, 2016 5:37:32 PM EDT, Vladimir Prus <[hidden email]> wrote:
>>
>> The release candidates for the 1.61.0 release are now available
>
> Thanks for your work to create this release, especially given the last minute breakages, etc.

Actually, we all need to thank Rene; the build automation he created was most excellent and allowed
to build packages auto-magically.

--
Vladimir Prus
http://vladimirprus.com


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

Re: Boost 1.61.0 Release Candidate 1

Tom Kent
In reply to this post by Vladimir Prus-4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 04/27/2016 04:37 PM, Vladimir Prus wrote:

>
> The release candidates for the 1.61.0 release are now available
> at:
>
> http://boost.cowic.de/rc/boost_1_61_0_rc1.zip 
> http://boost.cowic.de/rc/boost_1_61_0_rc1.7z 
> http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.bz2 
> http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz
>
> The SHA256 checksums are as follows:
>
> dcd11a91a412b2e8a78678b38cb2a74857e61f9bfe2577de9fd70be770100d54
> boost_1_61_0_rc1.7z
> 476937369c7a82103b734ccae85d35a523cdb7f8462c5f2fe1217ff0c8e2a7df
> boost_1_61_0_rc1.tar.bz2
> e60dee39ebb29d24bf8a4ef9aec34dbb8c1b9b219d4737ea4b358f38b1aab2b7
> boost_1_61_0_rc1.tar.gz
> e5f662f44a65c5c19450b8a1c07f75c7d5f16e58667871e856ba3984ec082006
> boost_1_61_0_rc1.zip
>
> As always, the release managers would appreciate it if you
> download the candidate of your choice and give building it a try.
> Please report both success and failure, and anything else that is
> noteworthy.
>
> The signed list of checksums is also attached, signed with the
> following key:
>
> https://pgp.mit.edu/pks/lookup?op=get&search=0xDA472E8659753BA4 Key
> fingerprint C5F0 F367 AA66 616F B839  806E DA47 2E86 5975 3BA4
>
I've verified that the downloads match the hashes, and that the signed
file that was attached verifies correctly.

Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJXIq1WAAoJEO5CwwL7YZSoapAP/2A4agot+juAH4QJj3jXKKz/
RyAgLg8XrNofSVKz4LfpygQBv1hc64b8TYm6V8Ln4iG62t/jd2aLiQGOLgOKDZNg
ZyjOncNmfvKGT9JQ3yhN+2zKsrm/cUrQ0RW/W/9+9XOwfe8Jhi0ywTNHrJTMe4vS
y+jQiUAWgV9WadHTlCFKftitMUATASez0WPH6FSQwzIUGrSqHKmAR1c3dSSzwIJM
O63xHCogg7K32GqC4evNIewf2T6LFtbcCFGydGa8iz3xqKEr3Y9lEJBK560/JXf+
ySqBTreAOvA+WMF7L5wNaNtjJJ0jWySi1JOcpY8VPsEyVwVgoDOlr90jc96dsDSA
DCN5RE3MGCAFv94weuFcrMqn2tVYWM70vavzywKsFGpUdLL9hR47xa6KXJy+dt8s
xt1kWjdIkwvbTrQcnWPhxmbq0GSxox55B61DzixzJfB33QNe2PaSWSc6gcylm5Bm
KNLOeYE5qffZZRNJmDapVniYPuv3SP+cQ7YeeFoW6ImWCOu7naMXBxEG8bsB6fsw
JGzwafetl2jKLbzVDjBHyb2x3/AvGq21+Qy0K4IAexPZuUY+EmMH0eE/GsZtM8N8
0rXWIdPBzyWAasrIIwfojmVmpylNQcrT4LEyPitSLYFKg3PKFABk2OuLbQuHLF/Y
x10B2OTnwI8NZghADrun
=nQXR
-----END PGP SIGNATURE-----

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

Re: Boost 1.61.0 Release Candidate 1

Carlos Ferreira
To when can the 1.61 release be expected?

Carlos

On 29 April 2016 at 01:39, Tom Kent <[hidden email]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> On 04/27/2016 04:37 PM, Vladimir Prus wrote:
> >
> > The release candidates for the 1.61.0 release are now available
> > at:
> >
> > http://boost.cowic.de/rc/boost_1_61_0_rc1.zip
> > http://boost.cowic.de/rc/boost_1_61_0_rc1.7z
> > http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.bz2
> > http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz
> >
> > The SHA256 checksums are as follows:
> >
> > dcd11a91a412b2e8a78678b38cb2a74857e61f9bfe2577de9fd70be770100d54
> > boost_1_61_0_rc1.7z
> > 476937369c7a82103b734ccae85d35a523cdb7f8462c5f2fe1217ff0c8e2a7df
> > boost_1_61_0_rc1.tar.bz2
> > e60dee39ebb29d24bf8a4ef9aec34dbb8c1b9b219d4737ea4b358f38b1aab2b7
> > boost_1_61_0_rc1.tar.gz
> > e5f662f44a65c5c19450b8a1c07f75c7d5f16e58667871e856ba3984ec082006
> > boost_1_61_0_rc1.zip
> >
> > As always, the release managers would appreciate it if you
> > download the candidate of your choice and give building it a try.
> > Please report both success and failure, and anything else that is
> > noteworthy.
> >
> > The signed list of checksums is also attached, signed with the
> > following key:
> >
> > https://pgp.mit.edu/pks/lookup?op=get&search=0xDA472E8659753BA4 Key
> > fingerprint C5F0 F367 AA66 616F B839  806E DA47 2E86 5975 3BA4
> >
> I've verified that the downloads match the hashes, and that the signed
> file that was attached verifies correctly.
>
> Tom
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQIcBAEBAgAGBQJXIq1WAAoJEO5CwwL7YZSoapAP/2A4agot+juAH4QJj3jXKKz/
> RyAgLg8XrNofSVKz4LfpygQBv1hc64b8TYm6V8Ln4iG62t/jd2aLiQGOLgOKDZNg
> ZyjOncNmfvKGT9JQ3yhN+2zKsrm/cUrQ0RW/W/9+9XOwfe8Jhi0ywTNHrJTMe4vS
> y+jQiUAWgV9WadHTlCFKftitMUATASez0WPH6FSQwzIUGrSqHKmAR1c3dSSzwIJM
> O63xHCogg7K32GqC4evNIewf2T6LFtbcCFGydGa8iz3xqKEr3Y9lEJBK560/JXf+
> ySqBTreAOvA+WMF7L5wNaNtjJJ0jWySi1JOcpY8VPsEyVwVgoDOlr90jc96dsDSA
> DCN5RE3MGCAFv94weuFcrMqn2tVYWM70vavzywKsFGpUdLL9hR47xa6KXJy+dt8s
> xt1kWjdIkwvbTrQcnWPhxmbq0GSxox55B61DzixzJfB33QNe2PaSWSc6gcylm5Bm
> KNLOeYE5qffZZRNJmDapVniYPuv3SP+cQ7YeeFoW6ImWCOu7naMXBxEG8bsB6fsw
> JGzwafetl2jKLbzVDjBHyb2x3/AvGq21+Qy0K4IAexPZuUY+EmMH0eE/GsZtM8N8
> 0rXWIdPBzyWAasrIIwfojmVmpylNQcrT4LEyPitSLYFKg3PKFABk2OuLbQuHLF/Y
> x10B2OTnwI8NZghADrun
> =nQXR
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>



--

Carlos Miguel Ferreira
Researcher at Telecommunications Institute
Aveiro - Portugal
Work E-mail - [hidden email]
Skype & GTalk -> [hidden email]
LinkedIn -> http://www.linkedin.com/in/carlosmferreira

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

Re: Boost 1.61.0 Release Candidate 1

Vladimir Prus-4
On 29.04.2016 13:45, Carlos Ferreira wrote:
> To when can the 1.61 release be expected?

Carlos,

This depends on the amount and nature of feedback we'll receive about the release candidate. Did you have
a chance to try it? What compiler did you use and what were the results?

Thanks,

--
Vladimir Prus
http://vladimirprus.com


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

Re: [EXTERNAL] Boost 1.61.0 Release Candidate 1

Belcourt, Kenneth
In reply to this post by Vladimir Prus-4

> On Apr 27, 2016, at 3:37 PM, Vladimir Prus <[hidden email]> wrote:
>
> The release candidates for the 1.61.0 release are now available at:
>
>    http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz

> As always, the release managers would appreciate it if you download
> the candidate of your choice and give building it a try. Please report
> both success and failure, and anything else that is noteworthy.

I built and installed with gcc-4.7.2, gcc-4.9.1, intel-12.1.6, and intel-16.0.2 on RH Linux, everything appears to be fine.  Many more warnings with Intel than Gcc.

One issue is that the gcc builds mangle the bin.v2 directory with the compiler version number, for example:

bin.v2/libs/thread/build/gcc-4.9.1/release

whereas the Intel builds do not include the version number.  Seems like we should update the intel-linux.jam to behave like gcc does, so we don’t end up with, for example:

bin.v2/libs/mpi/build/intel-linux/release

Not worth holding up the release for this but perhaps we should fix for the next release as it is error prone if you’re not paying close attention and building with multiple different Intel toolsets.

—- Noel


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

Re: [EXTERNAL] Boost 1.61.0 Release Candidate 1

Carlos Ferreira
@Vladimir

No, I did not tried the RC1 version, but since you are expecting feedback,
I will give it a try with the development version of Boost.Fiber (I really
want to use this, because it is so similar to Python's asyncio module).

I was just asking since the date at the Google Calender was not modified to
reflect the current release status.

Thank you for the info.

Carlos Ferreira

On 29 April 2016 at 20:19, Belcourt, Kenneth <[hidden email]> wrote:

>
> > On Apr 27, 2016, at 3:37 PM, Vladimir Prus <[hidden email]>
> wrote:
> >
> > The release candidates for the 1.61.0 release are now available at:
> >
> >    http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz
>
> > As always, the release managers would appreciate it if you download
> > the candidate of your choice and give building it a try. Please report
> > both success and failure, and anything else that is noteworthy.
>
> I built and installed with gcc-4.7.2, gcc-4.9.1, intel-12.1.6, and
> intel-16.0.2 on RH Linux, everything appears to be fine.  Many more
> warnings with Intel than Gcc.
>
> One issue is that the gcc builds mangle the bin.v2 directory with the
> compiler version number, for example:
>
> bin.v2/libs/thread/build/gcc-4.9.1/release
>
> whereas the Intel builds do not include the version number.  Seems like we
> should update the intel-linux.jam to behave like gcc does, so we don’t end
> up with, for example:
>
> bin.v2/libs/mpi/build/intel-linux/release
>
> Not worth holding up the release for this but perhaps we should fix for
> the next release as it is error prone if you’re not paying close attention
> and building with multiple different Intel toolsets.
>
> —- Noel
>
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>



--

Carlos Miguel Ferreira
Researcher at Telecommunications Institute
Aveiro - Portugal
Work E-mail - [hidden email]
Skype & GTalk -> [hidden email]
LinkedIn -> http://www.linkedin.com/in/carlosmferreira

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

Re: Boost 1.61.0 Release Candidate 1

Marcel Raad
In reply to this post by Vladimir Prus-4
Vladimir Prus-4 wrote
The release candidates for the 1.61.0 release are now available at:

[...]

As always, the release managers would appreciate it if you download
the candidate of your choice and give building it a try. Please report
both success and failure, and anything else that is noteworthy.
I compiled a few projects with it.
Signals2 is missing commit db0d3f55cccb2dbd8ab88a146af9100f2fca740b in master and thus doesn't work with Boost.Any and Boost.Variant on MSVC 14 Update 2.
Graph is still broken with MSVC 14 as commit 0fc1749bd7b300b0ad7a6ec45eefff5ea9057a0f is missing in master.
Everything else looked good.
Reply | Threaded
Open this post in threaded view
|

Re: [EXTERNAL] Boost 1.61.0 Release Candidate 1

Belcourt, Kenneth

> On Apr 30, 2016, at 7:34 AM, Marcel Raad <[hidden email]> wrote:
>
> Vladimir Prus-4 wrote
>> The release candidates for the 1.61.0 release are now available at:
>>
>> [...]
>>
>> As always, the release managers would appreciate it if you download
>> the candidate of your choice and give building it a try. Please report
>> both success and failure, and anything else that is noteworthy.
>
> I compiled a few projects with it.

> Graph is still broken with MSVC 14 as commit
> 0fc1749bd7b300b0ad7a6ec45eefff5ea9057a0f is missing in master.

Cherry picked this to master and tested on Darwin and Linux, both graph and graph_parallel are fine with this commit.



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

Re: Boost 1.61.0 Release Candidate 1

Murray Cumming
In reply to this post by Vladimir Prus-4
On Do, 2016-04-28 at 00:37 +0300, Vladimir Prus wrote:
> The release candidates for the 1.61.0 release are now available at:
>
>      http://boost.cowic.de/rc/boost_1_61_0_rc1.zip
>      http://boost.cowic.de/rc/boost_1_61_0_rc1.7z
>      http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.bz2
>      http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz
[snip]

Thanks.

This is a very minor issue, but I noticed that the boost graph examples
are missing a little fix that has been in develop (but not master)
since before 1.60 but it didn't get into 1.60 or this 1.61 release
candidate:
https://github.com/boostorg/graph/commit/63dd92da7247018f3291d48cfe04a5
7e51b48eb0

Isn't example code built as part of a release?

--
Murray Cumming
[hidden email]
www.murrayc.com




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

Re: Boost 1.61.0 Release Candidate 1

Mikhail Strelnikov
In reply to this post by Vladimir Prus-4
Looks like Boost.Compute is missing in <boost>/libs/libraries.htm.

Also <boost>/tools/regression/... referenced in <boost>/tools/index.html is
not included.


2016-04-28 0:37 GMT+03:00 Vladimir Prus <[hidden email]>:

>
> The release candidates for the 1.61.0 release are now available at:
>
>     http://boost.cowic.de/rc/boost_1_61_0_rc1.zip
>     http://boost.cowic.de/rc/boost_1_61_0_rc1.7z
>     http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.bz2
>     http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz
>
> The SHA256 checksums are as follows:
>
>     dcd11a91a412b2e8a78678b38cb2a74857e61f9bfe2577de9fd70be770100d54
> boost_1_61_0_rc1.7z
>     476937369c7a82103b734ccae85d35a523cdb7f8462c5f2fe1217ff0c8e2a7df
> boost_1_61_0_rc1.tar.bz2
>     e60dee39ebb29d24bf8a4ef9aec34dbb8c1b9b219d4737ea4b358f38b1aab2b7
> boost_1_61_0_rc1.tar.gz
>     e5f662f44a65c5c19450b8a1c07f75c7d5f16e58667871e856ba3984ec082006
> boost_1_61_0_rc1.zip
>
> As always, the release managers would appreciate it if you download
> the candidate of your choice and give building it a try. Please report
> both success and failure, and anything else that is noteworthy.
>
> The signed list of checksums is also attached, signed with the following
> key:
>
>     https://pgp.mit.edu/pks/lookup?op=get&search=0xDA472E8659753BA4
>     Key fingerprint C5F0 F367 AA66 616F B839  806E DA47 2E86 5975 3BA4
>
>
> Thanks!
>
> -- The release managers
>
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>

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

Re: Boost 1.61.0 Release Candidate 1

Vladimir Prus-4
In reply to this post by Murray Cumming
On 02.05.2016 11:07, Murray Cumming wrote:

> On Do, 2016-04-28 at 00:37 +0300, Vladimir Prus wrote:
>> The release candidates for the 1.61.0 release are now available at:
>>
>>      http://boost.cowic.de/rc/boost_1_61_0_rc1.zip
>>      http://boost.cowic.de/rc/boost_1_61_0_rc1.7z
>>      http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.bz2
>>      http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz
> [snip]
>
> Thanks.
>
> This is a very minor issue, but I noticed that the boost graph examples
> are missing a little fix that has been in develop (but not master)
> since before 1.60 but it didn't get into 1.60 or this 1.61 release
> candidate:
> https://github.com/boostorg/graph/commit/63dd92da7247018f3291d48cfe04a5
> 7e51b48eb0
>
> Isn't example code built as part of a release?

Murray,

I see that Noel has said he'd sync graph after the release, which should fix
your immediate concern.

As for examples, no, they are not automatically built at present. This is something
that would be good to change, but for 1.62 in the best case.

--
Vladimir Prus
http://vladimirprus.com


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

Re: Boost 1.61.0 Release Candidate 1

Robert Ramey
On 5/3/16 12:46 AM, Vladimir Prus wrote:

> On 02.05.2016 11:07, Murray Cumming wrote:
>> On Do, 2016-04-28 at 00:37 +0300, Vladimir Prus wrote:
>>> The release candidates for the 1.61.0 release are now available at:
>>>
>>>      http://boost.cowic.de/rc/boost_1_61_0_rc1.zip
>>>      http://boost.cowic.de/rc/boost_1_61_0_rc1.7z
>>>      http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.bz2
>>>      http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz
>> [snip]
>>
>> Thanks.
>>
>> This is a very minor issue, but I noticed that the boost graph examples
>> are missing a little fix that has been in develop (but not master)
>> since before 1.60 but it didn't get into 1.60 or this 1.61 release
>> candidate:
>> https://github.com/boostorg/graph/commit/63dd92da7247018f3291d48cfe04a5
>> 7e51b48eb0
>>
>> Isn't example code built as part of a release?
>
> Murray,
>
> I see that Noel has said he'd sync graph after the release, which should
> fix
> your immediate concern.
>
> As for examples, no, they are not automatically built at present. This
> is something
> that would be good to change, but for 1.62 in the best case.
>

I'm sure somewhere we have a "tool", git command, script or whatever
which can create a report which shows which libraries have differences
between develop and master branches in a concise way.  So maybe the
release procedure should start with a generation and display of this
report followed by nagging of developers to get them in sync. Once
they're in sync, developers would be admonished not to check into
develop until the master is checked.  One great thing about git is that
it lets me easily create a temporary local branch in which I can store
my local changes then merge them into develop as soon as the release
ships.  To summarize:

a) announce intention to ship master
b) encourage developers to sync develop to master
c) prepare summary report of differences
d) review tests on master branch, ship beta, etc.  cycle until done.
e) ship release, open master and develop for changes.

we want to maintain the distinction between master and develop.  But
during a hopefully short time, they should be in sync.

Robert Ramey




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