Re: [Boost-users] [1.55.0] Release candidates available

Subject: Re: [Boost-users] [1.55.0] Release candidates available
From: Marshall Clow (mclow.lists_at_[hidden])
Date: 2013-10-31 11:19:12

On Oct 31, 2013, at 6:49 AM, Shane Turner <shane.turner_at_[hidden]> wrote:
> On 31/10/2013 1:35 AM, Marshall Clow wrote:
>> Release candidate files for 1.55.0 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:
>> 	ba1ae723b8b4d1edeca684bb14b3213b	*boost_1_55_0_rc1.tar.gz
>> 	66e01be2f328c556835c42be7b6d17d5	*boost_1_55_0_rc1.tar.bz2 
>> 	925bb6c96082033687e5742b4e77af7b	*boost_1_55_0_rc1.zip 
>> 	830d61075ecf7d5ebf7c0843033393bf	*boost_1_55_0_rc1.7z 
>> 
>> Thanks!
> Several issues are still present in this release candidate.

Thanks for pointing these out!

> The following issues all still exist in this release candidate. Each issue has an appropriate patch already in Trac.
> boost/property_tree/detail/json_parser_write.hpp:35: warning: comparison is always true due to limited range of data type: https://svn.boost.org/trac/boost/ticket/5598
> Remove unused parameter warning in property tree json parser: https://svn.boost.org/trac/boost/ticket/6582
These two haven't been fixed in the trunk yet.

> Copy constructor for transform_width has an initialization order reversal: https://svn.boost.org/trac/boost/ticket/7990
This one was fixed in the trunk:
        Date: 2013-10-03 20:26:49 EDT (Thu, 03 Oct 2013)
        New Revision: 86155
but never merged to release.

> Output of "bcp build filesystem <output>" doesn't build: https://svn.boost.org/trac/boost/ticket/8812
I don't think that this has been fixed in the trunk yet.

> Is there a more expedient way to get fixes into Boost? Should I be contacting each maintainer directly?

That's what I would do, yes.

Bugs that haven't been fixed in trunk probably won't make it into the 1.55 release.
They'll need to be fixed on trunk, then we'll need time for all the testers to cycle to make sure that it didn't break anything.

-- 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