+1.

Martin Sebor wrote:
> I just created the next stdcxx 4.2.0 release candidate tag,
> stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
> pointed out in the original vote thread.
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
> 
> The tarball containing the release candidate sources can be
> downloaded from my home directory at the following link:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz 
> 
> 
> The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
> 
> Instructions on unpacking the tarball, configuring and building
> the library and the set of examples and tests, are in the README
> file contained in the tarball and can also be viewed directly
> in Subversion:
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
> 
> The Jira "Release Notes" for 4.2.0 detailing the issues resolved
> in this release can be viewed here:
> http://tinyurl.com/ytzonz
> 
> stdcxx 4.2.0 has been tested on the set of platforms listed in
> the README. The test results for most of the tested platforms
> can be be viewed on the following page:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
> (there are a few failures, most of them attributable to issues in
> the Rogue Wave test infrastructure; a small number of failures are
> due to known stdcxx issues).
> 
> Please download and test the tarball and vote to approve the
> release and to request the approval of the Incubator PMC to publish
> it on the stdcxx site. In your vote, please include the names and
> versions of the compilers and operating systems that you tested on.
> 
> As always, everyone is encouraged to vote, including non-committers.
> 
> This vote will close in the usual 72 hours from now, i.e., on
> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
> below for the countdown:
> http://tinyurl.com/2h5f73
> 
> 


-- 
Your fault - core dumped.