RE: Proposed branch tag performance patch for feature

[Kelly F. Hickel]

<snip>
> > I've gone to a fair amount of effort to follow the requirements for
> > changes, but at this point, before I spend more time on this I need
> to
> > fully understand *exactly* what is required to get these changes
> > committed. Particularly what is meant by the phrase "thoroughly
> tested
> > on feature".
> 
> That's open to interpretation/negotiation.  :-)
> 
> I haven't been following your progress closely, but from a distance it
> looks like you're pretty close to something that could reasonably be
> committed to the feature branch.
> 
> -Larry Jones
> 
> Oh, what the heck.  I'll do it. -- Calvin

The intention was that it be close, the reason I didn't tackle feature
first was that I don't believe I really understand CVS_LOCAL_BRANCH_NUM,
and how it complicates choosing a magic branch tag.

So, assuming this can get into a feature release, I need to decide
between running a
not-yet-approved-but-should-be-sometime-in-the-future-maybe patch
against 1.11, or running an approved-but-not-yet-released patch against
1.12.  Are there any good sources to help folks choose?  I've googled
and checked the wiki, but haven't really found anything except comparing
the 1.11 and 1.12 NEWS files.

For example, I seem to remember reading early last year that I didn't
need to do anything to my repo to switch, just start running cvs 1.12 as
the server, and things should "just work".  That would be important to
me, since I have a large number of platforms to support and so I'll have
a mix of 1.11 and 1.12 clients for the foreseeable future.


-Kelly