[1.35] proposal to add two platforms as release platforms for 1.35
I'd like to propose two additional platforms as release platforms for 1.35: 1. gcc-3.4.6_linux_ia64 (runner id: linux_ia64_gcc). It is all green on the trunk with Interprocess library marked as n/a. 2. gcc-4.2.1_hpux_ia64 (runner id: HP-UX_ia64_gcc). Three libraries are currently failing on trunk: Interprocess, Regex and Serialization. . Interprocess library: as for other HP platforms, this library will have to be marked n/a. I don't believe I'll have time to investigate failures and propose fixes in the 1.35 timeframe. . Regex library: fails because of the problem in <http://lists.boost.org/Archives/boost/2008/01/132318.php> The problem does not exist in release branch (and is fixed in trunk by <http://svn.boost.org/trac/boost/changeset/42745>) . Serialization library: test_exported* group of tests fail the same way they fail on all the platforms with gcc 4.1 and higher, including BGD-Ubuntu, which is a release platform for 1.35. I assume, this issue will be resolved before 1.35 is released and resolution will automatically cover gcc-4.2.1_hpux_ia64 as well. If I get a permission, I'll start testing these platform on the release branch, in addition to continuing testing on trunk. Thanks, Boris
Boris Gubenko wrote:
I'd like to propose two additional platforms as release platforms for 1.35:
I don't want to add any more platforms to 1.35.0. Every such change, no matter how small it seems, adds to the delay. We need to finish 1.35.0 and start working on the next release. I've no objection to adding a few more high priority platforms for the next release. --Beman
1. gcc-3.4.6_linux_ia64 (runner id: linux_ia64_gcc).
It is all green on the trunk with Interprocess library marked as n/a.
2. gcc-4.2.1_hpux_ia64 (runner id: HP-UX_ia64_gcc).
Three libraries are currently failing on trunk: Interprocess, Regex and Serialization.
. Interprocess library: as for other HP platforms, this library will have to be marked n/a. I don't believe I'll have time to investigate failures and propose fixes in the 1.35 timeframe.
. Regex library: fails because of the problem in <http://lists.boost.org/Archives/boost/2008/01/132318.php> The problem does not exist in release branch (and is fixed in trunk by <http://svn.boost.org/trac/boost/changeset/42745>)
. Serialization library: test_exported* group of tests fail the same way they fail on all the platforms with gcc 4.1 and higher, including BGD-Ubuntu, which is a release platform for 1.35. I assume, this issue will be resolved before 1.35 is released and resolution will automatically cover gcc-4.2.1_hpux_ia64 as well.
If I get a permission, I'll start testing these platform on the release branch, in addition to continuing testing on trunk.
Thanks, Boris
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Beman Dawes wrote:
I don't want to add any more platforms to 1.35.0. Every such change, no matter how small it seems, adds to the delay. We need to finish 1.35.0 and start working on the next release.
I understand the concern and this is why I'm proposing platforms which, based on test results, are ready for 1.35. Please, take into account the fact that some customers would not use Boost unless platform is tested and is listed as supported in a particular Boost release. Such customers would have to wait until "next release", whatever it means, which is unfortunate. I urge you to reconsider your decision. We can add the two platforms in question conditionally: run full tests against release branch and if the results are not as good as that on trunk, I'll remove zip archive(s) from the 1.35 ftp repository and it will be the end of the story. Thanks, Boris ----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: <boost@lists.boost.org> Sent: Monday, January 14, 2008 9:13 AM Subject: Re: [boost] [1.35] proposal to add two platforms as release platforms for 1.35
Boris Gubenko wrote:
I'd like to propose two additional platforms as release platforms for 1.35:
I don't want to add any more platforms to 1.35.0. Every such change, no matter how small it seems, adds to the delay. We need to finish 1.35.0 and start working on the next release.
I've no objection to adding a few more high priority platforms for the next release.
--Beman
1. gcc-3.4.6_linux_ia64 (runner id: linux_ia64_gcc).
It is all green on the trunk with Interprocess library marked as n/a.
2. gcc-4.2.1_hpux_ia64 (runner id: HP-UX_ia64_gcc).
Three libraries are currently failing on trunk: Interprocess, Regex and Serialization.
. Interprocess library: as for other HP platforms, this library will have to be marked n/a. I don't believe I'll have time to investigate failures and propose fixes in the 1.35 timeframe.
. Regex library: fails because of the problem in <http://lists.boost.org/Archives/boost/2008/01/132318.php> The problem does not exist in release branch (and is fixed in trunk by <http://svn.boost.org/trac/boost/changeset/42745>)
. Serialization library: test_exported* group of tests fail the same way they fail on all the platforms with gcc 4.1 and higher, including BGD-Ubuntu, which is a release platform for 1.35. I assume, this issue will be resolved before 1.35 is released and resolution will automatically cover gcc-4.2.1_hpux_ia64 as well.
If I get a permission, I'll start testing these platform on the release branch, in addition to continuing testing on trunk.
Thanks, Boris
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
on Mon Jan 14 2008, "Boris Gubenko" <Boris.Gubenko-AT-hp.com> wrote:
Beman Dawes wrote:
I don't want to add any more platforms to 1.35.0. Every such change, no matter how small it seems, adds to the delay. We need to finish 1.35.0 and start working on the next release.
I understand the concern and this is why I'm proposing platforms which, based on test results, are ready for 1.35.
Please, take into account the fact that some customers would not use Boost unless platform is tested and is listed as supported in a particular Boost release. Such customers would have to wait until "next release", whatever it means, which is unfortunate.
I urge you to reconsider your decision. We can add the two platforms in question conditionally: run full tests against release branch and if the results are not as good as that on trunk, I'll remove zip archive(s) from the 1.35 ftp repository and it will be the end of the story.
This sounds reasonable to me. Beman? -- Dave Abrahams Boost Consulting http://boost-consulting.com
participants (3)
-
Beman Dawes -
Boris Gubenko -
David Abrahams