Ralph Goers wrote:
The code freeze for the 2.1.8 release starts tonight and ends next friday (hopefully) with the release of 2.1.8.The usual committing rules for a code freeze apply.
We're on subversion right?What's wrong with creating a branch for 2.1.8 release candidate and finishing that off without freezing all of development work?
Even better, all transactions are atomic (so we won't have half commits or half branches) and the merging works alot better.
