zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: Zookeeper protocol weirdness and pure Python kazoo client
Date Fri, 31 Aug 2012 20:02:40 GMT
Donating code to apache doesn't prevent you from having your own release
cycle on github.  Your releases just won't be Apache releases.  It also
doesn't prevent you from pushing diffs for kazoo for Apache trunk.  That
way you can release whenever you like and Apache can bundle the current
stable version of kazoo with each release.  It might be nice to push a new
stable just before each ZK release, but that isn't critical if the stable
release more or less keeps up with your bleeding edge.

On Fri, Aug 31, 2012 at 12:39 PM, Ben Bangert <ben@groovie.org> wrote:

> > I'd love to see kazoo get contributed back to Apache. Is that something
> > you're interested in doing? I'm not sure we can wholesale replace the
> > extant Python bindings because I know we have users that depend upon
> them -
> > but that's a solvable problem, it's no great pain to include both in a
> > release.
> It probably depends on what that means. It's been incredibly convenient to
> be on github for the easy pull request merging and tracking other forks. It
> seems like the code in the zookeeper contrib/ tree has its release schedule
> tied to Zookeeper itself, which seems like a bad decision to me since it
> means that client releases are tied to Zookeeper releases rather than being
> able to quickly push out new client releases when important bug fixes have
> been applied. Perhaps that's not the case, it's not entirely clear to me.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message