[zeromq-dev] Stopping zmq_device

Pieter Hintjens ph at imatix.com
Fri Jul 9 12:13:22 CEST 2010

On Fri, Jul 9, 2010 at 8:41 AM, Martin Sustrik <sustrik at 250bpm.com> wrote:

> There's really no way out except for separating stable and experimental
> trees.

This seems obvious, as it's obvious that while some people are
experimenting on a new unstable branch, others are carefully
maintaining the older stable branch.  The questions seem to be:

* how we number versions (I'd suggest 2.1.0 become a new unstable and
2.0.x progress towards bugfree stability).
* when we can make API changes (I'd suggest no further API changes in 2.0.x).
* whether stable versions get internal changes (I'd suggest, bug fixes
and optimizations, but not new features).

The biggest downstream cost will be to force language bindings to
maintain two versions but we've heard that this won't be a problem,
from at least some bindings maintainers.


More information about the zeromq-dev mailing list