Closed toddpalino closed 7 years ago
Would love a release to test this particular fix: https://github.com/python-zk/kazoo/pull/393
EDIT: People can temporary test master
by editing requirements.txt
if they use such a file:
-e git+git://github.com/python-zk/kazoo@c67f3468285a9fd5f9479859dfb1aeb528f3c86e#egg=kazoo
. Works for us for now since we're running our software in contained containers. But would love to see a release!
@harlowja, any possibility of this? Or are there blockers that can be worked on?
Seems like it should be ok with me; though I do need to double check.
Any objections from @bbangert @hannosch @rgs1 (or others)?
Sounds fine to me.
Bump
Beginning release.
Bump
Hm, I'm bumping this again.
Is there any other Contributors that are able to initiate the process of releasing this?
If there is anything holding back the release then it would be nice to see issues references to this issue so maybe we can help out with killings bugs before you are confident with releasing.
Thanks.
@harlowja or @bbangert, can we please get a release cut for this?
Sure, I'll cut a release on Tuesday (Monday is holiday here), and I'd prefer not to cut a release on Friday afternoon just in case any emergency bug releases are needed afterwards (it's been awhile since a release).
Closing this as I'll be issuing the release shortly now that the PR's are cleaned up. Still reviewing and updating the changelog, should be out today or tomorrow!
Would it be possible to cut a new release from master (potentially 2.3.0)? There have been a lot of updates since the last release, which was 1.5 years ago, that are only in master. Many of us use released versions only and not being able to pick up these updates is problematic.