Boost regression notification (2005-11-01 [RC_1_33_0])
Boost regression test failures ------------------------------ Report time: 2005-11-01T14:47:09Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/is... 0 failure in 0 library:
This report lists all regression test failures on release platforms.
Detailed report:
http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/is...
0 failure in 0 library:
Eureka! :-) John.
We now have zero failures on the RC_1_33_0 branch. The RC_1_33_0 is now closed for all commits: write to me *directly* if there is something that absolutely must go into the 1.33.1 release. I will be rolling the release tarballs shortly. Doug On Nov 1, 2005, at 12:00 PM, Douglas Gregor wrote:
Boost regression test failures ------------------------------ Report time: 2005-11-01T14:47:09Z
This report lists all regression test failures on release platforms.
Detailed report:
http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/ developer/issues.html
0 failure in 0 library:
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
We now have zero failures on the RC_1_33_0 branch. The RC_1_33_0 is now closed for all commits: write to me *directly* if there is something that absolutely must go into the 1.33.1 release. I will be rolling the release tarballs shortly.
I wouldn't mind fixing the configure script issues that were reported earlier, but it's clearly not going to affect any code, and I don't think it should hold up a Beta release of 1.33.1 either. Besides we may get more reports like this from a Beta test. In other words: lets ship it :-) John.
On 11/01/2005 12:19 PM, Doug Gregor wrote:
We now have zero failures on the RC_1_33_0 branch. The RC_1_33_0 is now closed for all commits: write to me *directly* if there is something that absolutely must go into the 1.33.1 release. I will be rolling the release tarballs shortly.
Doug, I'm afraid I neglected to run libs/mpl/preprocessed/preprocess.py mentioned here: http://article.gmane.org/gmane.comp.lib.boost.devel/132302 in order to recreate all the mpl files in boost/mpl/preprocessed. I guess I should wait till after this release to do that? Sorry for my forgetfulness. -Larry
On Nov 2, 2005, at 1:14 PM, Larry Evans wrote:
On 11/01/2005 12:19 PM, Doug Gregor wrote:
We now have zero failures on the RC_1_33_0 branch. The RC_1_33_0 is now closed for all commits: write to me *directly* if there is something that absolutely must go into the 1.33.1 release. I will be rolling the release tarballs shortly.
Doug,
I'm afraid I neglected to run libs/mpl/preprocessed/preprocess.py mentioned here:
http://article.gmane.org/gmane.comp.lib.boost.devel/132302
in order to recreate all the mpl files in boost/mpl/preprocessed. I guess I should wait till after this release to do that?
Please wait until after the release. CVS HEAD would be the best place to do this, actually; the RC_1_33_0 branch might not continue after 1.33.1. Doug
participants (5)
-
Caleb Epstein -
Doug Gregor -
Douglas Gregor
-
John Maddock -
Larry Evans