[zeromq-dev] Proposal for next stable release

Pieter Hintjens ph at imatix.com
Mon Mar 19 01:10:45 CET 2012

n Sun, Mar 18, 2012 at 5:46 PM, Paul Colomiets <paul at colomiets.name> wrote:

> The project SHALL NOT use topic branches.
> Needs more explanation.

1. All experimentation happens outside the main repository until it's
ready for public use and then
2. It's pushed as rapidly as possible to master so that it gets critical review.

This is driven by several observations:

* Topic branches tend to remain untested for a long time, which is bad
because it increases the change latency (time for changes to hit
critical review by users).

* Mixing development and process in a single repository creates
complex git structures, which is bad because it makes the repository
structure harder to learn and more error-prone.

* Mixing maintenance and contributor roles creates complex
responsibilities, which is bad because few people can play both roles

In effect we're using forked repos to replace topic branches.


More information about the zeromq-dev mailing list