canmove, Confirmed users
2,056
edits
| Line 83: | Line 83: | ||
hg tag 0.3 | hg tag 0.3 | ||
{{note|you tag the repository with the release candidate version | {{note|you tag the repository with the final version in addition to the release candidate version because the code you are tagging is potentially both the code you ship in the RC and the code you ship in the final release, if you find no problems with it that require spinning another RC. You also do it because then you can bundle the code into a directory named after the final release using Mercurial's built-in tag-based archiving feature, as described below.}} | ||
{{note|if this is a second or subsequent release candidate, you have to specify the <tt>--force</tt> flag to <tt>hg tag</tt> for the final version (i.e. <tt>hg tag --force 0.3</tt> in order to update the existing tag.}} | |||
Push the changes to the central repository: | Push the changes to the central repository: | ||