[help] Development strategy(SVN to Mercurial)
Tal
tal_hd at hotmail.com
Mon Jan 31 08:41:26 CST 2011
I have been using SVN, so back then the way was simpler.
Like most of the SVN owner, I have had 3 directories:
./branch/ : Means it's should work better than older version(usually less
stable than beta).
./trunk/ : The head of the development, means that it's not ready to general
use, but it is a way for all the developers will have the latest source
code. The common code is under ./trunk/src/ and the separated feature work
is under ./trunk/name(see tag now).
./tag/name/ : Like branches, but contain only a unique feature that haven't
merge to the development(i.e. branch).
Sorry if I have made a mistake about the SVN, I hope you've knew it already.
Now in Mercurial, the strategy have to be different! So I use this way:
instead of directories, I use branches(not "./branch/" directory):
default: Same as ./branch/ in SVN, for the global code&feature.
trunk: Same as ./trunk/src/ in SVN.
You can see how I have done it so far:
http://maxdream.hg.sourceforge.net/hgweb/maxdream/maxdream/
http://maxdream.hg.sourceforge.net/hgweb/maxdreamdefault/maxdream/
You may have already guessed I use "hg branch -f branchName" for swapping
from one brunch head to another(hg told me I need to use "-f").
I also consider using this:
default/name : Same as ./tags/name/ in SVN.(Can I use "/" in branch name? If
not, "-" will be good also)
trunk/name : Same as ./trunk/name/ in SVN.
Can I use it for my project? I haven't found a good answer in web-search.
Again, please see the link to the repo. I gave above.
--
View this message in context: http://mercurial.808500.n3.nabble.com/help-Development-strategy-SVN-to-Mercurial-tp2389578p2389578.html
Sent from the General mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20110131/e4219b89/attachment.htm>
More information about the Mercurial
mailing list