stdcxx-dev mailing list archives

Speaking of other changes that might need to be integrated
before we tag the branch, here are a couple more:
https://issues.apache.org/jira/browse/STDCXX-479
https://issues.apache.org/jira/browse/STDCXX-481
Martin
Martin Sebor wrote:
> Andrew, we should be using the -rcN tag rather than the branch
> directly. The latest tag is 4.2.0-rc-2. Unless there are other
> changes that you need to integrate we should tag the 4.2.0
> branch again and make a 4.2.0-rc-3.
>
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-2/
>
> Martin
>
> Andrew Black wrote:
>> Greetings all.
>>
>> A couple months ago, a 4.2.0 pre-release branch was created in
>> subversion. This branch allows for interested parties to preview the
>> upcoming release, with the understanding that the code isn't final.
>>
>> Within RogueWave, we recently stated using this branch as part of our
>> nightly testing process for the rest of our SourcePro family of
>> products. However, the 4.2.0 branch, at this time, contains a serious
>> bug in the code reported as
>> https://issues.apache.org/jira/browse/STDCXX-482 , and resolved in
>> http://svn.apache.org/viewvc?view=rev&rev=555106 . This bug leads to an
>> infinite loop while attempting to run the LIMITS.cpp config test.
>>
>> The nightly testing system for SourcePro is shared with STDCXX, and
>> hangs during the nightly testing process for SourcePro affect STDCXX by
>> preventing STDCXX builds from running. Therefore, unless any objections
>> are voiced, it is my intent to branch LIMITS.cpp from trunk to the 4.2.0
>> branch in the next day or so.
>>
>> --Andrew Black
>