I'll recreate the issue there. I can see how C4 could be considered more democratic and less authoritarian than git flow since anyone can fork for stabilization (equivalent to creating a release branch in git flow). I also see how it could be less error-prone to create a feature fork rather than a feature branch. But fundamentally I don't see any significant differences in the two processes....both go from features/bugfixes, to a probably-good-but-unblessed state, to a stabilization (bugfix and testing only) state, to a released state.
> On Dec 8, 2013, at 2:06 PM, Pieter Hintjens <[email protected]> wrote: > > We have moved the issue tracker to github and you may want to create > new issues there. No urgency, it'll be a gradual migration. > > The process is... not the same as gitflow. The subtleties will become > clear to you over time. It's far more aimed at learning, and less at > organization, as a goal. > > -Pieter > > >> On Sun, Dec 8, 2013 at 6:34 PM, Lindley French <[email protected]> wrote: >> I've created a JIRA issue: >> https://zeromq.jira.com/browse/LIBZMQ-589 >> >> Next I'll try to figure out how to properly apply C4 to this process. I'm >> more familiar with gitflow, and while C4 appears to be pretty much the same >> thing except with forks instead of branches, I'm sure there are subtleties. >> >> >>> On Sat, Dec 7, 2013 at 4:23 AM, Arnaud Loonstra <[email protected]> wrote: >>> >>>> On 12/07/2013 12:15 AM, Lindley French wrote: >>>> Is there a better place for discussion of this effort? I do have a lot >>>> of questions. >>>> >>>> The latest one is about encoder_t etc. This appears to have changed >>>> significantly recently, and I'm not entirely sure how to adapt the >>>> Crossroads code to match. Is there documentation on its latest design >>>> somewhere? >>> No please continue your quest out in the open. I would like to keep >>> track as well. Do you have a repository online somewhere? >>> >>> Arnaud. >>> >>> -- >>> w: http://www.sphaero.org >>> t: http://twitter.com/sphaero >>> g: http://github.com/sphaero >>> i: freenode: sphaero_z25 >>> _______________________________________________ >>> 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 > _______________________________________________ > 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
