[zeromq-dev] Proposal for libzmq maintenance

Philip Kovacs kovacsp3 at comcast.net
Tue Jan 10 00:10:36 CET 2012

* Pieter Hintjens <ph at imatix.com> [2012-01-09 16:58:54 -0600]:

> To contribute a new feature, one forks libzmq, writes and tests the
> feature and makes a pull request. All pull requests would be
> automatically published to zeromq-dev for review and comment. When a
> feature gets consensus approval the maintainers merge the pull request
> onto master. From then on, it will be included in automatic builds and
> tested by early adopters.
> To contribute a bug fix, one forks libzmq, writes and tests the bug
> fix, and makes a pull request to master. The maintainers check that
> there is a proper test case (for fixes to stable branches) and retest
> the fix after merging the pull request. The maintainers then merge
> that fix to the various branches it affects, and the bug fix is then
> included in automatic builds of that branch and will go into new
> packages.

> Comments and discussion welcome.
> -Pieter

Would the above "new feature" procedure also be used for the language 
bindings, e.g. czmq? I note that czmq already uses the fork/pull request 
procedure for bug fixes.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
Url : http://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120109/3090e88d/attachment.pgp 

More information about the zeromq-dev mailing list