Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>In your example, you are creating <a href="http://mercurial.selenic.com/wiki/Tag" rel="nofollow">tags</a>, not (named) <a href="http://mercurial.selenic.com/wiki/NamedBranches" rel="nofollow">branches</a>. Tags won't help you to create separate lines of development: they are just stand-alone identifiers assigned with particular revisions.</p> <h2>Creating branches</h2> <p>To start using branches, you probably want to review some tutorials, such as:</p> <ul> <li><a href="http://hgbook.red-bean.com/read/managing-releases-and-branchy-development.html" rel="nofollow">Chapter 8. Managing releases and branchy development</a> (from Bryan O'Sullivan's book)</li> <li><a href="http://stevelosh.com/blog/2009/08/a-guide-to-branching-in-mercurial/" rel="nofollow">A Guide to Branching in Mercurial</a> (Steve Losh)</li> </ul> <p>Based on your description, you probably want to create <code>prod</code> and <code>qa</code> branches based on your current <code>default</code> branch, as well as any feature / topic branches you might want for radical changes.</p> <p>Once you have these branches in place, it's very easy to compare them, merge between them, see what changes are pending from one to the other, and so on as your workflow demands.</p> <h2>Bundles</h2> <blockquote> <ol> <li>Play around with Bundles and see if they can help us but seems quite complicated</li> </ol> </blockquote> <p>If you only have FTP access, then bundles probably won't help you. You could upload a bundle to the server via FTP, but you would need to be able to run <code>hg</code> on the server to unpack the bundle into a repository.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload