Stable release patch policy

To lower the risk of insufficiently tested code breaking ØMQ stable releases (which has happened a couple of times recently), we recommend (and use ourselves) this policy for moving patches into a stable release:

Every patch MUST be identified by a clean issue (i.e. one that covers precisely that problem).

Email the release announcement to zeromq-dev and (separately) to zeromq-announce, so that Reply-To works properly.

Announce the release on Freshmeat, Twitter, and the #zeromq IRC channel.

Precautions: don't make an official release immediately after applying changes. Allow at least one day for the automated builds to test on all platforms. If the changes are not 100% safe, ask for review of the repository master on email or IRC.

Setting a new version number

Set the new version number immediately after a release, so that the release repository always holds the next in progress version. The version number is located in {{include/zmq.h}: