RE: [Monotone-devel] Re: newbie: Life after cvs-import

[Kelly F. Hickel]

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On
Behalf Of
> Ulf Ochsenfahrt
> Sent: Tuesday, November 21, 2006 3:57 AM
> To: address@hidden
> Subject: Re: [Monotone-devel] Re: newbie: Life after cvs-import
> 
> Brian May wrote:
> > I tend to agree. Unless:
> >
> > * You have to continue using CVS for some reason.
> >
> > * You expect to frequently need access to old versions and don't
want
> > to have to resort to using CVS for such cases.
> 
> You checkout the stable branch from cvs. You then add all the files
into
> mtn and commit. Then you checkout the development branch from CVS
(into
> the same directory!) add all changed files, drop all removed files,
and
> commit into a development branch.
> 
> Then you got
> * stable
> |\
> | \
> |  * development
> |  |
> |  | continue to work on development
> |  .
> | continue to work on stable
> .
> 
> and at some later point
> .
> |
> *  .
>   \ |
>    \|
>     * can merge from stable into development

[Kelly F. Hickel] Well, this is an interesting idea.  In practice, I
think (for us) that it would be fairly tricky.  At any given moment, we
probably have between 6 and 8 supported, active releases at customer
sites.  Each of those releases has a maintenance branch, and a "hotfix"
branch where fixes are made for critical issues. In addition, we'd
likely be working on 2 as yet unreleased version.  There would also be
any number of in progress projects or bug fixes going on in their own
branches.

So, determining the right branches to bring over, and the correct order
in which to import them would seem to be possible (it *must* be
possible, right? Otherwise the repo is already "useless"), it certainly
isn't trivial...

I'll have to give this one some thought...

Thanks,
Kelly

> 
> > The second point might be significant if, for example, there is a
> > stable branch of the product in CVS and you don't want to keep using
> > CVS to maintain the stable branch.
> 
> I agree with your coworker as well. If the import didn't work, and you
> don't know it didn't, then the whole 1+ GB of archive may be
essentially
> useless.
> 
> -- Ulf