Re: [boost] 1.51.0] Beta 1 release candidate 2 available

Subject: Re: [boost] 1.51.0] Beta 1 release candidate 2 available
From: Marshall Clow (mclow.lists_at_[hidden])
Date: 2012-08-02 22:18:58

On Aug 2, 2012, at 11:58 AM, Tom Kent <lists_at_[hidden]> wrote:

> On Wed, Aug 1, 2012 at 4:42 PM, Marshall Clow <mclow.lists_at_[hidden]> wrote:
> 
>> Release candidate files for 1.51.0 beta 1 are available at
>> http://boost.cowic.de/rc/
>> 
>> 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.
>> 
>> This helps ensure the candidates build OK before we push them out to
>> SourceForge.
>> 
>> The files (and associated md5s) are:
>>        e3a51b82894a67ac438eaa08192929eb
>> *boost_1_51_0_beta1_rc2.tar.gz
>>        1c541236f98dcaa706e7f8eabb11ebfc
>> *boost_1_51_0_beta1_rc2.tar.bz2
>>        964f150ce9d7bcaba74255aba73d338a        *boost_1_51_0_beta1_rc2.zip
>>        e23467c3369a53189300c76e8c848aa1        *boost_1_51_0_beta1_rc2.7z
>> 
>> Thanks to everyone who tried out rc1, and especially Neal Becker, who
>> helped me track down a permissions error in the build process
>> 
>> --The release managers
>> 
> 
> Works for me.
> 
> Builds under VC8, VC9, VC10 for 32 & 64 bit.
> 
> Links/Runs with a test exe on all those platforms in debug and release
> configurations.
> 
> One suggestion for the release process: can we use sha256 sums? I've dumped
> md5 from all my processes, its not a huge deal but if we're going to have
> cryptographic checksums we might as well do the ones that work.

Ok, you've whetted my curiosity.
What "doesn't work" in md5?
I'm aware of the attacks against it.

-- Marshall

Marshall Clow     Idio Software   <mailto:mclow.lists_at_[hidden]>

A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait).
        -- Yu Suzuki