Flavio,
thanks for your reply.
If I understand you correctly, you are saying that the 3.5.0 release in
itself can be considered stable in terms of software quality, but the
feature set may change during the 3.5 maintenance cycle? If so, is it
likely that 3.5 releases will introduce incompatible changes in terms of
ensemble and client-server combination?
Also, would you say that that 3.5.0 and it's new features can be used in
production?
Cheers,
Sam
On 2015-03-21 12:29, Flavio Junqueira wrote:
Hi Sam,
The label "alpha" refers to an alpha release of the 3.5 branch, not an
alpha version of 3.5.0. We typically only have bug fixes for the minor
releases of a branch, and for 3.5, we have used alpha to say that the
release is indeed unstable and that major changes could come with
later releases of the branch.
I suppose we could have done 3.5.0-alpha, 3.5.0-beta, 3.5.0 or some
similar sequence, but that isn't the current thinking afaict.
-Flavio
On 21 Mar 2015, at 09:08, 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
