[Cppunit-devel] FAQ / 1.8 branch

[Steve M. R. <ste...@vi...>]

On Tue, Sep 25, 2001 at 05:54:02PM +0200, Baptiste Lepilleur wrote:
> Quoting "Steve M. Robbins" <ste...@vi...>:

 
> > From my point of view, I prefer text.  If we find ourselves wanting
> > fancy things, like links, then we can move to straight HTML, or to
> > something that can be processed into HTML.  We could use Doxygen,
> > for example, as done in doc/other_documentation.dox.  Doxygen has
> > an easy way to make lists, I believe.  And it would be *very* easy
> > to hyperlink both to and from the CppUnit class documentation, so
> > that might be the best option.
> 
>   Yes, linking to the doc would be interesting. Can Doxygen generate a TOC ?

Mmmm.  If it does, I don't know how to do that.
You can, however, make "groups" of bits of documentation, and
you automatically get a "group" page.  That might be good enough.

But, anyway, we have only three questions at this point.  Let's just
do _something_ now and figure out the niceties if it gets to be a
burden.

 
> > >   How do we go reporting fix into the 1.8.0 branch ?
> > 
> > Well, since there is no branch done yet, everything on the "main"
> > trunk will appear in both the 1.6.1 and 1.8.0 release.  So please
> > do commit bugfixes onto the CVS tree.
> > 
> > Once a branch is made, then the procedure is: checkout the 1.6 branch,
> > make the change, commit it.  Then check out the main branch and merge
> > in the change just made on the 1.6 branch.  This is a mildly more
> > difficult procedure, so I am delaying making a 1.6 branch in order
> > that we can continue to use the simpler procedure.  
> > 
> > We can delay a 1.6 branch until we need to make 1.8-only changes to
> > CVS.  I thought we'd give it a week or so, until the bugfixes die
> > down.  What do you think?
> 
>   Well, I already have some features (CPPUNIT_TEST_EXCEPTION) I would like to 
> add (I would target 1.8.0 for the end of next week. Expected exception and 
> named suite registration only would be worth it).

Well, so far, we aren't exactly inundated with bug reports.  So making
the change at the end of next week is probably fine.

At any rate, ONCE the branch is made, the idea is to merge 1.6.x
bugfix changes to the main trunk (if applicable) as you do them.
Any delay of the merge just makes it more complicated.

-Steve

P.S. I guess the lack of bug reports is good, unless it means that
nobody is using CppUnit.  We are getting a bunch of traffic though:
check out the "stats" page if you haven't already done so.


-- 
by Rocket to the Moon,
by Airplane to the Rocket,
by Taxi to the Airport,
by Frontdoor to the Taxi,
by throwing back the blanket and laying down the legs ...
- They Might Be Giants