[zeromq-dev] Upcoming stable 2.1 release - devices

[Pieter Hintjens]

On Mon, Mar 14, 2011 at 6:38 AM, Martin Sustrik <sustrik at 250bpm.com> wrote:

> As it's backward incompatible, it violates the release policies:
> "You can apply new update [third version number] to your production
> environment safely."

Thanks for that opinion. These programs were undocumented and
unmaintained, and thus do not in my view constitute part of any API,
no matter how broad.

Secondly, I'd expect that people upgrading to 2.1 stable will be
coming from 2.0, and in any case cannot apply that safely, due to
changes in the zmq_term semantics, as we already know.

Lastly, it would be insane to have to make a 2.2 release just to
remove these junk programs from the distribution. If our policies
force us to do insane things, the policies are broken and need repair.

However, I'm more interested in feedback from actual users, and as
necessary we'll fix the rules to reflect reality, rather than trying
to vainly apply rules that interfere with sane practice, and don't
help where it actually matters.

> Also, backporting the 3.0 changes will be a merge nightmare later on.

That is not true as far as I can see. Removing these extraneous files
from the release package has no effect on the actual 0MQ code. Please
explain your reasoning?

-Pieter