Re: [Boost-users] [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Richard Sent: 17 March 2015 17:20 To: boost@lists.boost.org Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
Another quarter has gone by and another Boost release is prepared for beta and I see *no* changes to Boost.Test listed in the release notes.> So here we are, waiting another 3 months for *simple* changes to be reflected in this library while the maintainer insists that the fixes are available, yet they continue not to be deployed into any shipping release.
It is indeed really deplorable that we don't have Boost.Test updates in a release. Though in mitigation I note that we are really struggling to get out a GIT-driven release at all, (and some of the new troubles are with asynch-exceptions in Boost.Test. See this thread Re: [boost] Running b2 on develop needs asynch-exceptions=on.) However, Richard's hard work on improved docs have been refined and completed by Raffi Enficiaud. Many bug fixes are in the develop branch (including some very new and prompt bug fixes, for example https://svn.boost.org/trac/boost/ticket/11054). I also understand that the fear of Boost.Test updates causing trouble with other libraries, and worse with users test, is a cause for caution in a release version. So it would be really good if *lots more users could download and use the version in the Boost.Test develop branch* so we can get current user feedback. (My experience is good using this, and the test matrix is also good). You can download just Boost.Test either using GIT or as a zip from https://github.com/boostorg/test/tree/develop and substitute it for the contents of the current release modular-boost/libs/test folder (Don't forget to rebuild the Boost.Test library unless you only use the included version). If nothing else, you will find Raffi's shiny new Boostbook docs finally allow you to find what you want to know without frustration. I'd very much like to see this new docs version in the 1.58 documentation release (despite any new features not being in the code release). Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
On March 18, 2015 4:49:31 AM CDT, "Paul A. Bristow" <pbristow@hetp.u-net.com> wrote:
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Richard Sent: 17 March 2015 17:20 To: boost@lists.boost.org Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
Another quarter has gone by and another Boost release is prepared for beta and I see *no* changes to Boost.Test listed in the release notes.> So here we are, waiting another 3 months for *simple* changes to be reflected in this library while the maintainer insists that the fixes are available, yet they continue not to be deployed into any shipping release.
It is indeed really deplorable that we don't have Boost.Test updates in a release.
Though in mitigation I note that we are really struggling to get out a GIT-driven release at all, (and some of the new troubles are with asynch-exceptions in Boost.Test.
Understanding this is one man's opinion outside looking in, taken with a grain of salt... Taking nothing whatsoever away from the effort behind the scenes, reporters, maintainers, etc. It's been how many release cycles since a migration to git? Git newbies or not, how hard is it to handle pull requests, pin submodule revisions, and so on? Master it for one, rinse, repeat, and move on. It seems to me from other posts that Test is not the only part that suffers from this pattern.
See this thread Re: [boost] Running b2 on develop needs asynch-exceptions=on.)
However, Richard's hard work on improved docs have been refined and completed by Raffi Enficiaud.
Many bug fixes are in the develop branch (including some very new and prompt bug fixes, for example https://svn.boost.org/trac/boost/ticket/11054).
I also understand that the fear of Boost.Test updates causing trouble with other libraries, and worse with users test, is a cause for caution in a release version.
So it would be really good if
*lots more users could download and use the version in the Boost.Test develop branch*
so we can get current user feedback. (My experience is good using this, and the test matrix is also good).
You can download just Boost.Test either using GIT or as a zip from
https://github.com/boostorg/test/tree/develop
and substitute it for the contents of the current release modular-boost/libs/test folder
(Don't forget to rebuild the Boost.Test library unless you only use the included version).
If nothing else, you will find Raffi's shiny new Boostbook docs finally allow you to find what you want to know without frustration.
I'd very much like to see this new docs version in the 1.58 documentation release (despite any new features not being in the code release).
Paul
--- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
On 3/18/2015 5:49 AM, Paul A. Bristow wrote:
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Richard Sent: 17 March 2015 17:20 To: boost@lists.boost.org Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
Another quarter has gone by and another Boost release is prepared for beta and I see *no* changes to Boost.Test listed in the release notes.> So here we are, waiting another 3 months for *simple* changes to be reflected in this library while the maintainer insists that the fixes are available, yet they continue not to be deployed into any shipping release.
It is indeed really deplorable that we don't have Boost.Test updates in a release.
Though in mitigation I note that we are really struggling to get out a GIT-driven release at all, (and some of the new troubles are with asynch-exceptions in Boost.Test. See this thread Re: [boost] Running b2 on develop needs asynch-exceptions=on.)
However, Richard's hard work on improved docs have been refined and completed by Raffi Enficiaud.
Many bug fixes are in the develop branch (including some very new and prompt bug fixes, for example https://svn.boost.org/trac/boost/ticket/11054).
I also understand that the fear of Boost.Test updates causing trouble with other libraries, and worse with users test, is a cause for caution in a release version.
So it would be really good if
*lots more users could download and use the version in the Boost.Test develop branch*
so we can get current user feedback. (My experience is good using this, and the test matrix is also good).
You can download just Boost.Test either using GIT or as a zip from
https://github.com/boostorg/test/tree/develop
and substitute it for the contents of the current release modular-boost/libs/test folder
(Don't forget to rebuild the Boost.Test library unless you only use the included version).
If nothing else, you will find Raffi's shiny new Boostbook docs finally allow you to find what you want to know without frustration.
I'd very much like to see this new docs version in the 1.58 documentation release (despite any new features not being in the code release).
Do I have to rebuild the Boost.Test library to get the new docs ? Because the first thing I did was to try to view the new docs by opening index.html only to find that there was no html documentation. Then I tried 'b2 toolset=gcc-4.9.2' for building Boost.Test and received: Performing configuration checks - symlinks supported : yes error: Unable to find file or target named error: 'dyn_ut_example.cpp' error: referred to from project at error: '../../libs/test/example' It does not appear that the 'develop' branch is ready for me at all.
Le 18/03/15 14:43, Edward Diener a écrit :
On 3/18/2015 5:49 AM, Paul A. Bristow wrote:
Do I have to rebuild the Boost.Test library to get the new docs ? Because the first thing I did was to try to view the new docs by opening index.html only to find that there was no html documentation. Then I tried 'b2 toolset=gcc-4.9.2' for building Boost.Test and received:
Performing configuration checks
- symlinks supported : yes error: Unable to find file or target named error: 'dyn_ut_example.cpp' error: referred to from project at error: '../../libs/test/example'
It does not appear that the 'develop' branch is ready for me at all.
This is the location of the new documentation: http://www.boost.org/doc/libs/develop/libs/test/doc/html/index.html I do not know about the update frequency In order to build the doc: cd $boost/libs/test/doc ../../../bjam -sDOCBOOK_XSL_DIR=/some/path/docbook-xsl-1.78.1/ -sDOCBOOK_DTD_DIR=/some/path/docbook-xml-4.2/ Doxygen should be in the $PATH. The previous command will build whatever is necessary. Best, Raffi
Paul A. Bristow <pbristow <at> hetp.u- net.com> writes:
So it would be really good if
*lots more users could download and use the version in the Boost.Test develop branch*
so we can get current user feedback.
I regularly use the develop version on my local development machine and never had any problems, apart from always having to replace new occurrences of BOOST_MESSAGE with BOOST_TEST_MESSAGE.
Paul A. Bristow <pbristow <at> hetp.u- net.com> writes:
I also understand that the fear of Boost.Test updates causing trouble with other libraries, and worse with users test, is a cause for caution in a release version.
So it would be really good if
*lots more users could download and use the version in the Boost.Test develop branch*
so we can get current user feedback. (My experience is good using this, and the test matrix is also good).
Could someone merge https://github.com/boostorg/ptr_container/ pull/2 please? One of the commits is needed for PtrContainer's master regression tests to compile with the develop version of Boost.Test.
participants (6)
-
Edward Diener -
Marcel Raad -
Michael -
Paul A. Bristow -
Raffi Enficiaud