Hi all, > > Are the benefits worth the trouble? And what happens with our history > > if we move to git?
> I don't know this. There are tools to migrate Subversion, for example, > that I know of. I don';t know of a CVS one nor whether the history comes > too. > > I think a V3 branch in the existing repository is probably the best > idea. We can (I assume) copy the existing docs into the V3 and then edit > them to be more V3 specific? AFAICT from the reactions so far, moving to git isn't worth the trouble. It may be better than CVS, but our commit rate is so low and our demands so simple that it probably doesn't matter which VCS we use, so let's stick with the one we have. Now, how are we going to organize the branches? Currently we have the trunk and the B_Release branch. Everything is in the trunk, and in addition, (recent) publishable versions of our docs are in B_Release as well. If we start a single separate branch for V3, it will contain both publishable versions and intermediate stuff. Do we want this? We can use tags to mark finished docs of course, but - contrary to the core code - they won't be synchronized. We could also create a V3 working branch and a V3_Release branch. Or keep all the intermediate stuff in the trunk and commit releasable Firebird 3 docs to a single V3(_Release) branch... Any ideas? Cheers, Paul Vinkenoog ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
