Mato,

There is already a section on this, let me know what is missing or wrong...

-Pieter
On Jan 30, 2012 12:11 PM, "Martin Lucina" <[email protected]> wrote:

> Pieter,
>
> [email protected] said:
> > Thus, I'd advise people to send patches early, rather than late, since
> > it takes about 6 months for new code to make its way into a stable
> > release. If you time it right, you can roll into production on a
> > stable release that contains the fixes you depend on.
>
> The current process does a great job of documenting how one can get code
> into the official libzmq master, and also how bugfixes are applied to and
> reviewed for the current stable release (i.e. 2.1).
>
> What is missing is documentation on how / when a release / branch is
> declared "stable", or as you write above, how "code makes its way into a
> stable release".
>
> Cheers
>
> -mato
>
> _______________________________________________
> zeromq-dev mailing list
> [email protected]
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to