Andrew Black wrote:
> My concern about using -rc-6 as the 4.2.0 release is that there are
> still several flaws in the readme file that have yet to be addressed.
> See my note in
> http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200710.mbox/%3c4715163A.6000908@...%3e > providing a list of these discrepancies. I provided a patch for the
> issues in section 10 (which need to be propagated to the website), but I
> am busy with other projects at work, and don't have time to work on the
> section 4 and 6 issues I noted.
Ugh. I thought you had covered all the issues in your patch.
I should have read your post more carefully. Let me work on
sections 4.4, and 6. I could use help with section 4.6, the
Windows build directory structure and Windows installation.
I'm not sure if Farid's still online after pulling an
allnighter last night. If not, Travis, can you give it a try?
> --Andrew Black
> Martin Sebor wrote:
>> I created what I'm hoping will be the final stdcxx 4.2.0 release
>> candidate, stdcxx-4.2.0-rc-6:
>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/ >>
>> along with a tarball containing the sources:
>> http://people.apache.org/~sebor/stdcxx/stdcxx-incubating-4.2.0.tar.gz >>
>> The MD5 sum for the tarball is: f65ea507f7d82688d1cf241bce25dc01
>> Instructions on unpacking the tarball, configuring the library,
>> and building it along with the set of examples and tests, are
>> in the README file contained in the tarball. The file can also
>> be viewed directly in Subversion:
>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/README >>
>> The Jira "Release Notes" for 4.2.0 detailing the vast number of
>> issues resolved in this release can be found 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/results/ >> (there are some failures, most of them due to the Rogue Wave test
>> infrastructure and IT issues; please disregard those).
>> Please take the tarball for a spin and vote to approve the release
>> and to request the approval of the Incubator PMC to publish it on
>> our site.
>> Everyone is encouraged to vote, including non-committers.
>> This vote will close in the usual 72 hours.