[zeromq-dev] 0MQ/3.0, 0MQ/4.0 and 0MQ process

[Martin Sustrik]

On 10/31/2011 01:46 AM, MinRK wrote:

> I believe GitHub can make the 'pull request is an email' happen
> automatically with hooks.  Of course, that could fork discussion between
> those doing review on GitHub and those doing it on the mailing list,
> which might be more annoying than it's worth.
>
> I will note as a data point that for us (IPython), the move to GitHub a
> year ago increased community contributions and participation by an order
> of magnitude.  Not git in general, but GitHub in particular.

Ack. Still, it's not like 100% of developers are using git today (e.g. 
OpenVMS team). I believe some way of contributing patches using diffs 
should exist.

> As for the rollback of 4.0, are there commits in 4.0 that are not in 3.0
> that would want to be kept in the new 3.0-tracking master?  I'm just
> confused as to why the reverting would happen if the plan is simply to
> make 3.0 master, and 4.0 'experimental', when you can just rename
> libzmq/master to libzmq/experimental, and push current zeromq3-0/master
> as libzmq/master.

How would that solve the problem of separating the "stable" patchsets 
from "experimental" patchsets? Whatever way you take you have to 
manually inspect all the patches and move them either onto "stable" 
branch or on individual topic branches.

I am not against better way of doing this -- it would save me large 
amount of ultimately boring unpaid work -- however, I don't see any 
other way out at the moment.

Thoughts?
Martin