> I have no problem with setting up such a branch for you, as long as
> "catching up" is done in reasonably sized chunks of work, not one or
> two strings at a time.
I think I mean two different things.
1) Since we are working on the branch, just switching to trunk will be a
lot of work. Since I am currently using svk to mirror, and I didn't mirror
the whole repository, it will be a pain now to set that up. I would rather
just start working in the real repository.
2) Once we are "caught up", then I would probably manage it like you have
been doing the locking branch. Just do a weekly, or perhaps even 2-3
weeks, catch-up merge of changes.
I have no idea if/when this code would ever be accepted into trunk, perhaps
parts of it will and other will need to be maintained. Assuming that is
the case, I will probably want to setup a "mirror" of the Subversion
structure in my branch. So I would have a trunk that was keeping up with
trunk, and I would need branches for releases, just as you do.
I am certainly willing to follow whatever direction and guidance people
want to provide. A good place to start would be -- would it be OK to
commit what we have as a "code bomb" to our branch, or would you want to
see us go back and retroactively commit this in chunks with detailed log
messages etc... That could be hard initially, as we have 9 months of work
in this, but after that, it wouldn't be a problem.
Thanks
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 10 23:14:37 2005