The plan is to build the 1.36.0 beta release Sunday. Developers who have permission to make last minute fixes and docs updates should commit those changes by midnight Saturday, UTC. --Beman
Beman Dawes <bdawes <at> acm.org> writes:
The plan is to build the 1.36.0 beta release Sunday.
Developers who have permission to make last minute fixes and docs updates should commit those changes by midnight Saturday, UTC.
Can I check in and merge docs? Gennadiy P.S. I really prefer Boost.Test trunk to be used for this release (did not realize I had to do anything), but it's less critical.
Gennadiy Rozental wrote:
Beman Dawes <bdawes <at> acm.org> writes:
The plan is to build the 1.36.0 beta release Sunday.
Developers who have permission to make last minute fixes and docs updates should commit those changes by midnight Saturday, UTC.
Can I check in and merge docs?
Yes. Please do a single commit so it is easy to revert if needed.
Gennadiy
P.S. I really prefer Boost.Test trunk to be used for this release (did not realize I had to do anything), but it's less critical.
There are probably others in the same boat, but it is too late to take a chance on destablizing Boost.Test. --Beman
There are two tests from two different libraries that do not compile on HP-UX/ia64 with aC++ A.06.17 : gil/pixel and python/object (comment.html used to say: A.06.14, I fixed it to specify the correct version of the compiler being used). In both cases, compilation failures are almost certainly caused by new version of EDG Front End implementing Core Issue 574. In our bug tracking system, it is treated as QuIX ID: QXCR1000804484. Would it be possible to markup these two tests for the release branch? If so, I can do it before a deadline. Thanks, Boris -----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Beman Dawes Sent: Friday, July 25, 2008 11:06 AM To: Boost Developers Mailing List Subject: [boost] [1.36.0] Beta release imminent The plan is to build the 1.36.0 beta release Sunday. Developers who have permission to make last minute fixes and docs updates should commit those changes by midnight Saturday, UTC. --Beman _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Gubenko, Boris wrote:
There are two tests from two different libraries that do not compile on HP-UX/ia64 with aC++ A.06.17 : gil/pixel and python/object (comment.html used to say: A.06.14, I fixed it to specify the correct version of the compiler being used).
In both cases, compilation failures are almost certainly caused by new version of EDG Front End implementing Core Issue 574. In our bug tracking system, it is treated as QuIX ID: QXCR1000804484.
Would it be possible to markup these two tests for the release branch? If so, I can do it before a deadline.
Yes, but please do so right away. Thanks, --Beman
Cannot do it. Something had happened to my SVN access: Authentication realm: <https://svn.boost.org:443> Boost SVN repository Subversion Access Username: bgubenko Password for 'bgubenko': Authentication realm: <https://svn.boost.org:443> Boost SVN repository Subversion Access Username: bgubenko Password for 'bgubenko': svn: Commit failed (details follow): svn: MKACTIVITY of '/svn/boost/!svn/act/...': authorization failed (https://svn.boost.org) I have a validated explicit-failures-markup.xml file with the fix. I can send it (as an attachment) to somebody who does not have this problem. Or, may be, this problem with SVN access has an easy fix. I'll be able to check my mail again around 3 A.M. Eastern time. Thanks, Boris
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Beman Dawes Sent: Friday, July 25, 2008 4:04 PM To: boost@lists.boost.org Subject: Re: [boost] [1.36.0] Beta release imminent
Gubenko, Boris wrote:
There are two tests from two different libraries that do not compile on HP-UX/ia64 with aC++ A.06.17 : gil/pixel and python/object (comment.html used to say: A.06.14, I fixed it to specify the correct version of the compiler being used).
In both cases, compilation failures are almost certainly caused by new version of EDG Front End implementing Core Issue 574. In our bug tracking system, it is treated as QuIX ID: QXCR1000804484.
Would it be possible to markup these two tests for the release branch? If so, I can do it before a deadline.
Yes, but please do so right away.
Thanks,
--Beman
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Attached the patch. If some good soul with write access to SVN can apply it to the release branch before a Saturday midnight deadline, I'll be grateful. Thanks, Boris Index: status/explicit-failures-markup.xml =================================================================== --- status/explicit-failures-markup.xml (revision 47825) +++ status/explicit-failures-markup.xml (working copy) @@ -1729,7 +1729,16 @@ </mark-expected-failures> </library> + <!-- gil --> + <library name="gil"> + <mark-expected-failures> + <test name="pixel"/> + <toolset name="acc"/> + <note author="Boris Gubenko" refid="46"/> + </mark-expected-failures> + </library> + <!-- graph --> <library name="graph"> <mark-unusable> @@ -4093,6 +4102,11 @@ </note> </mark-expected-failures> <mark-expected-failures> + <test name="object"/> + <toolset name="acc"/> + <note author="Boris Gubenko" refid="46"/> + </mark-expected-failures> + <mark-expected-failures> <test name="args"/> <test name="auto_ptr"/> <test name="builtin_convertors"/> @@ -6100,4 +6114,10 @@ problem. </note> + <note id="46"> + The test does not compile, most likely because of new version of EDG Front End + implementing Core Issue 574. In the HP bug tracking system, it is tracked as + QuIX ID: QXCR1000804484. + </note> + </explicit-failures-markup>
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Gubenko, Boris Sent: Friday, July 25, 2008 5:07 PM To: boost@lists.boost.org Subject: Re: [boost] [1.36.0] Beta release imminent
Cannot do it. Something had happened to my SVN access:
Authentication realm: <https://svn.boost.org:443> Boost SVN repository Subversion Access Username: bgubenko Password for 'bgubenko': Authentication realm: <https://svn.boost.org:443> Boost SVN repository Subversion Access Username: bgubenko Password for 'bgubenko': svn: Commit failed (details follow): svn: MKACTIVITY of '/svn/boost/!svn/act/...': authorization failed (https://svn.boost.org)
I have a validated explicit-failures-markup.xml file with the fix. I can send it (as an attachment) to somebody who does not have this problem. Or, may be, this problem with SVN access has an easy fix. I'll be able to check my mail again around 3 A.M. Eastern time.
Thanks, Boris
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Beman Dawes Sent: Friday, July 25, 2008 4:04 PM To: boost@lists.boost.org Subject: Re: [boost] [1.36.0] Beta release imminent
Gubenko, Boris wrote:
There are two tests from two different libraries that do not compile on HP-UX/ia64 with aC++ A.06.17 : gil/pixel and python/object (comment.html used to say: A.06.14, I fixed it to specify the correct version of the compiler being used).
In both cases, compilation failures are almost certainly caused by new version of EDG Front End implementing Core Issue 574. In our bug tracking system, it is treated as QuIX ID: QXCR1000804484.
Would it be possible to markup these two tests for the release branch? If so, I can do it before a deadline.
Yes, but please do so right away.
Thanks,
--Beman
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Hi Boris.
Attached the patch. If some good soul with write access to SVN can apply it to the release branch before a Saturday midnight deadline, I'll be grateful.
Your patch has been applied to the release branch. Changeset link: http://svn.boost.org/trac/boost/changeset/47828 Best regards, Jurko Gospodnetić
Hi Jurko, thanks a lot! -boris
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Jurko Gospodnetic Sent: Saturday, July 26, 2008 4:59 AM To: boost@lists.boost.org Subject: Re: [boost] [1.36.0] Beta release imminent [Boris Gubenko's patch applied]
Hi Boris.
Attached the patch. If some good soul with write access to SVN can apply it to the release branch before a Saturday midnight deadline, I'll be grateful.
Your patch has been applied to the release branch.
Changeset link: http://svn.boost.org/trac/boost/changeset/47828
Best regards, Jurko Gospodnetić
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Beman Dawes <bdawes@acm.org> writes:
The plan is to build the 1.36.0 beta release Sunday.
Developers who have permission to make last minute fixes and docs updates should commit those changes by midnight Saturday, UTC.
Please can I merge the latest documentation changes for Boost.Thread? Anthony -- Anthony Williams | Just Software Solutions Ltd Custom Software Development | http://www.justsoftwaresolutions.co.uk Registered in England, Company Number 5478976. Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL
Anthony Williams wrote:
Beman Dawes <bdawes@acm.org> writes:
The plan is to build the 1.36.0 beta release Sunday.
Developers who have permission to make last minute fixes and docs updates should commit those changes by midnight Saturday, UTC.
Please can I merge the latest documentation changes for Boost.Thread?
Yes, please do. --Beman
participants (5)
-
Anthony Williams -
Beman Dawes -
Gennadiy Rozental -
Gubenko, Boris -
Jurko Gospodnetić