[zeromq-dev] Discuss: 0MQ releases and stability

Pieter Hintjens ph at imatix.com
Wed Feb 16 17:16:45 CET 2011

On Wed, Feb 16, 2011 at 5:01 PM, Martin Sustrik <sustrik at 250bpm.com> wrote:

> I would propose just doing it.
> Fork the master from a convenient point in the project history. Backport any
> subsequent patches that should go into stable. Make a release. It should
> take at most couple of days.
> Let's see then whether people can be attracted into submitting patches for
> the stable.

Presumably this means you, as a developer, would be unwilling to
submit pull requests for bugs you fix. Right? So that requires someone
to track all commits, match them manually against bug reports on IRC
and email, (since you don't use the Github issue tracker
systematically), prepare patches for the interesting ones, and send
them as pull requests or apply them as patches...


More information about the zeromq-dev mailing list