RE: [Cppunit-devel] ch-ch-ch-changes ...

[Townsend, G. <gto...@sh...>]

> BTW this makes me very curious about how many people are 
> using CppUnit in a production environment.

FWIW, I had just started to play with CppUnit before it became a SF project.
I have been using 1.5.5, but only the very basics because there is so much
change going on. I don't want to have to change everything later. So for now
I'm just using TestCase  and TestSuite, with a commandline interface to show
results. There are a lot of improvements happening so I am willing to wait a
little while. But I really want to have a CppUnit project under source
control, and which all of my other projects can  use. And of course I don't
want all my projects to break because an interface changed in CppUnit.

Regarding the current changes being made: It seems to me that if people were
using the original version before it became an active project, then they
have the choice to continue to use that version or upgrade to the SF version
and get a cleaner design and more functionality. But sometime fairly soon, I
do think that CppUnit should get a very stable interface such that people
can depend on. Previously I think it was CppUnit was explicitly not
supported by Michael Feather. Now that it's a SF project, people will expect
that it is a serious tool that they can count on to maintain backwards
compatibility. 

That said, the Development Status of CppUnit on SF is shown as Pre-Alpha. I
cannot imagine any reasonable person (developer) thinking that Pre-Alpha
means things are not changing! ( Seems that the development status probably
is ready to be changed on the next release to at least something much closer
to Released status. ) Once the status gets to a beta status, then changes
that might break code become worthy of a lot more concern and thought.

Guy