Have you considered using feature toggles for such situations? Would allow you to release a non-alpha 3.5.0 with the big new feature off by default and those wanting to try it can do so trivially.
Karol > On 10 Sep 2015, at 20:51, Ivan Kelly <[email protected]> wrote: > > Is 3.5.0-alpha even so alpha? The big change is reconfig, and from a quick > look at the code, the majority of that doesn't get touched if you don't use > the reconfig feature. The rest of the server code look pretty much the same > as 3.4 apart from a few bug fixes. > > -Ivan > >> On Thu, Sep 10, 2015 at 9:16 PM Chris Conroy <[email protected]> wrote: >> >> On a related note: intention to cut a 3.5.1-alpha release was announced in >> early February yet it was only just released. This seems like a very long >> window for an alpha quality release. Why not just cut a new point release >> rather than wait for all of the minor issues to be resolved? >> >> This long timeframe was a bit frustrating since I was waiting on the >> release to see if it fixes the looped NPE issue that we hit quite >> frequently in development. Eventually I gave up and cut an internal release >> for our users. >> >> I was a bit surprised to see multiple alpha release candidates. Also, the >> release candidates are tagged with the same version of 3.5.1-alpha instead >> of e.g. 3.5.1-alpha-rc1 which means all of our maven/nexus caches won't be >> able to pick up the official release without being manually cleared! Could >> we please tag the release candidates with different versions in the future? >> >> On Sat, Mar 21, 2015 at 5:08 AM, Sam Weisberg <[email protected] >> wrote: >> >>> Hi list, >>> >>> I am a little confused about the versioning of the 3.5 release branch. >>> When looking at the homepage, it sais the 3.5 release "is alpha quality" >>> and it is suffixed with a -alpha tag. >>> >>> When I first looked at the github releases[1] however, it seams to >>> indicate that there has already been a 3.5 release candidate and a 3.5 >>> release. >>> In addition, the devs seem to be gearing up for a 3.5.1 release[2], which >>> would be curious if there was not even a stable 3.5.0 release. >>> There is also no longer an active milestone for 3.5.0 in Jira. >>> >>> Considering all that, I have a bit of trouble understanding the >>> implications of the -alpha suffix of the 3.5.0 release. >>> Can the 3.5.0 release be considered stable and is just not widely used? >>> I would appreciate it if someone could clarify this for me a bit. >>> >>> Cheers, >>> Sam >>> >>> [1] https://github.com/apache/zookeeper/releases >>> [2] >> https://mail-archives.apache.org/mod_mbox/zookeeper-dev/201502.mbox/%3CCANLc_9JktxbnYuyW2EbvFEcRoaZWMsPf38YdoM=5jlwlusz...@mail.gmail.com%3E >>
