Hi all, Yesterday I have rewritten the documentation of the release process [0]. It was still a mix of my (in the meantime outdated) SVN documentation and the new Hg based process.
I found that using Hg is much more comfortable than using SVN. Initially I feared that the lack of branch information in the email notification would handicap the synchronization between the integration and the release branch. In the past I would use my inbox to track changes to SVN applicable for synchronization. Using `hg view`, `hg import` and `hg export` is easier than tracking the changes in my inbox. Moreover, since everything happens locally, it is much faster than SVN and there is more tolerance for experimentation: commit as much as you want, then check everything with `hg view` again before pushing. If things go really badly, you can pull a fresh version and start again without affecting the project. Most of the process documentation should be up to date, however, if you find the occasional outdated information; and if you are confident about how to fix it, please fix. And if you are not sure, or if something does not work for you, please ask here. Yuv [0] http://wiki.panotools.org/Development_of_Open_Source_tools#Processes
signature.asc
Description: This is a digitally signed message part.
