I did create that release branch in the end, but by a manipulation mistake, I ended up pushing the current HEAD instead of just the current release tag. Oh well. There is no code difference, happily, only enhanced documentation and a test cleanup. But from now on, I'll be using separate checkouts so there is less room for blunder. Next time someone makes a code change in HEAD that is not going to be released as part of 2.0, I propose he should bump the version to 2.100. When the 2.100 branch has matured enough, we can release 2.200 or 2.500 or 3.000 or whatever. Hopefully, the project remains simple enough that we don't need multiple dots in version names as in 2.6.27.47, but come what may. In any case, the master branch is open for commits. But please don't break it - test before you push. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] As the Chinese say, 1001 words is worth more than a picture. — John McCarthy