Several issues are still present in this release candidate. 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!
-- The release managers _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users 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 * Copy constructor for transform_width has an initialization order reversal: https://svn.boost.org/trac/boost/ticket/7990 * Output of "bcp build filesystem <output>" doesn't build: https://svn.boost.org/trac/boost/ticket/8812 Is there a more expedient way to get fixes into Boost? Should I be contacting each maintainer directly? -- Shane Turner Senior Software Developer phone +1 (902) 406--8375 x1008 email Shane.Turner@NewPace.ca mailto:Shane.Turner@newpace.ca aim aim:GoIm?screenname=Shane.Turner@newpace.ca/msn msnim:chat?contact=Shane.Turner@newpace.ca Shane.Turner@NewPace.ca aim:GoIm?screenname=Shane.Turner@newpace.ca skype saturnjct skype:saturnjct