[zeromq-dev] EFSM not always raised in 2.1.8

Pieter Hintjens ph at imatix.com
Sun Jul 31 23:12:16 CEST 2011

Hi MinRK,

> I see that you renamed 2.1.8 to 2.1.8-rc. I can't cut a pyzmq release
> with code labeled as a release candidate, and this change has also
> broken a few tools that track the current zeromq release (e.g.
> homebrew) which had updated to point to 2.1.8 which no longer exists.

Hmm. Sorry about that. I guess there's some experimentation still
going on with release names.

> Does the fact that 2.1.8 is now an rc mean that there will not be a
> 2.1.8 release, and I should wait for 2.1.9, and tell homebrew to
> rollback to 2.1.7 for now?

Yes. I'm reluctant to reuse release numbers, so the next release would
be 2.1.9. The -rc is to make absolutely clear to users that it
contains less than 100% mature code (that large backport to remove the
socketpair limitations). I should have marked it -rc to start with, my

You'll see that historic releases also now have -alpha and -beta tags
to indicate their maturity.

The alternative to adding an -rc tag was to delete the release and
rollback to 2.1.7 but that leaves gaps, which isn't nice either.

Sorry for the awkwardness... and thanks a lot for having tested that
2.1.8 release and finding the issue.


More information about the zeromq-dev mailing list