On Fri, 27 Aug 2004 13:33:04 +0900, Jamis Buck <jgb3 / email.byu.edu>
wrote:
> Sorry to post this question here, but it IS marginally
> Ruby-related...
> 
> [ahem] anyway, here goes.
> 
> I just finished rewriting Copland, almost from the ground up. I'll
> be announcing the new version soon(ish), but I need to get it into
> CVS. Now, there's already an existing implementation of Copland in
> CVS, but I'd (obviously) like to replace it with the new version.
> 
> What is the best way to go about this? Right now, I'm leaning
> towards doing a "cvs delete" on the existing implementation, and
> then checking in the new implementation on top of it. Thus, the
> existing version history is maintained, etc. Is there a better way
> to do this?
> 
> Another option is to create a new module in CVS, calling it
> "copland2" or something. However, Copland is really still in a
> "pre-1.0" state, and I don't want to give the wrong impression by
> artificially bumping it to a post-1.0 version number. The rewrite
> was necessary to add some new functionality (like fail-fast and
> better schema validation), but on the surface there really isn't
> anything new...
> 
> Anyway, suggestions from anyone older-and-wiser would be
> appreciated. Thanks!

I would tag the existing version -- and perhaps even branch it. All
of my programs and libraries are tagged and branched on major
releases (e.g., X.0.0 or X.Y.0). A notable exception is Ruwiki
0.8.0; it will not be branched until 0.8.1 becuase of some known
large changes that I want to carry forward to 0.9 even with planned
bugfixes.

At any rate, tag and branch copland as it stands. Then, do a CVS
delete on those files that no longer exist in copland. After adding
the new files, update, then tag and branch again.

-austin
-- 
Austin Ziegler * halostatue / gmail.com
               * Alternate: austin / halostatue.ca