It's happening!

This is going to mean a few changes to our development process, but I don't think we will have too many growing pains. There are still some unanswered questions, like if we want to really manage pull requests or let every developer have write access to the central repository, but we can figure out what works best for us as we go along. In the process of this transition, I deleted all the old branches in the subversion repository because they really weren't useful any longer, and I wanted to start our Mercurial repository with a clean slate. Unfortunately, we lost the release tags made to our subversion repository in the transition as well. I don't think this is a huge loss, and we can re-tag them if really care to do so.
Old project home: https://sourceforge.net/projects/allacrost/
The repository on sourceforge is now in read-only mode. No one has access to write to it, not even myself (although I have the ability to restore write-access for anyone). You should no longer try to commit code there, and should no longer be able to do so anyway. The project page on sourceforge will remain for now, but eventually I plan to edit this page to point to the new home on bitbucket, and will probably remove all the release files as well due to sourceforge's new habit of distributing malware in release project binaries. As I mentioned on the front page of the site, I plan to take offline our old bug tracker at bugs.allacrost.org and use bitbucket's issue tracker instead. This will be easier for us, because maintaining the bug tracker was just one more thing we had to do that I would rather not spend our time on. We'll see how things go.
Everything is still in a state of flux, so changes will keep happening for a while until we've settled into our new groove. Documentation pages need to be updated, etc. I'll try to keep this thread updated with any important developments. If you have any questions related to this transition or new development processes, please ask away.