RE: repository structure question...

> So, I'm looking for some advice on what sort of repository
> organization
> might best support both the maintenance of these divergent source
> trees,
> and their reintegration over time, and also on what the best way might
> be to bring these sources into subversion, whether we should simply
> import them as separate trunks (treating them as separate products, I
> guess) or as branches, or if perhaps some sort of multi-step process
> (e.g., importing the "primary" source to a trunk, importing the
> "secondary" variants as branches, creating additional branches (or
> trunks) off the "primary", merging the "secondaries" to these new
> branches (or trunks) to create a record of the differences... or
> something like that.) would be best.

I think you're on the right track for thinking about how to structure your repository. I would pick a "primary" based on the least number of differences (in other words, most similarity) with all the others, to reduce the amount of merging. You may even want to make this "primary" a branch from which you will create a "trunk" after you rip out the parts that you don't usually want in your trunk. It does sound, however, like you want to understand your code better before you dive into this exercise...

HTH,
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Olivier Dagenais
Software Engineering / Génie logiciel
Formark - Combine the Best of SharePoint® and Livelink®
Phone: 613-599-5173 ext 238
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Make sure you don't miss anything: subscribe to the Formark Newsletter:
http://www.formark.com/support/register/index.asp
Received on Tue May 8 16:00:10 2007