This is probably only of interest to those who use the PN source code,
if you don’t then feel free to move right along!
Now that Google Code supports Mercurial for source control I’m considering whether to move PN to this. Mercurial provides a much better model for managing Open Source project source control as it allows each user to maintain a local set of changes with full change history without needing project approval for commits. Any changes that the project is interested in taking can then be pulled into the main project tree.
Unless there are any major objections to the move I’ll start working on the import soon. The source at it’s final subversion revision will remain available in subversion indefinitely, but new commits will only go to the mercurial repository.
More on Mercurial:
All feedback welcome, here or in the forums.
Is there a simple mechanism for keeping an Hg and Svn repo in sync?
On Windows, I don’t think that Hg has a client as nice as TortoiseSVN, and that can be an important issue.
I agree with Matt that a tightly integrated Windows client like TortoiseSVN is really key for some developers. It’s one of the reasons that keeps me using it and keeps me on Windows!
I’d be interested in hearing more about the experience you have switching to Mercurial and what client you end up using.
It’s not perhaps as fully polished as TortoiseSVN yet, but TortoiseHg looks to be quite usable and in active development:
http://bitbucket.org/tortoisehg/stable/wiki/Home
I’m investigating Subversion and Mercurial synchronization.
@Simon
Moving to Hg and building PN was not difficult at all, strictly from the console.
Although TortoiseHg is not as polished as the Svn counterpart, it seems to to the job just fine.