I think assuming the latest release would be unstable is confusing and not in line with other Apache projects. If you want to have a instable prerelease version, I would suggest to call it a beta version and once the major bugs are removed, a new stable release could be provided.
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.
Am 21.03.17, 16:41, moon soo Lee <[hidden email]> schrieb:
Thanks for the opinion. Yes we can think about proper label. These are labels mentioned in this threads so far.
'Unstable', 'Stable', 'Old'
'Latest', 'Stable', 'Old'
'Beta', 'Stable', 'Old'
Intention is not that we want to release 'unstable' version, i think.
The intention is give user proper expectation that latest release may(and may not) include bug which we couldn't discovered in verification process like what happened in our previous release 0.7.0 and 0.6.0.
These are how other apache projects describe their releases.
Kafka - x.x.z is the latest release. current stable version is x.y.z.
Flink - x.y.z is our latest stable release
Cassandra - even-numbered contains new features, odd-numbered contains bug fixes only
Spark - available 2.1.0, 2.0.2, 2.0.1, 2.0.0 .... 1.4.0 as a 'stable' release, others are available as 'archived' releases.
Mesos - most recent stable release: x.y.z
Hadoop - 'x.y.z-alpha' or 'x.y.z' or 'x.y.z (stable)'
Hbase - 1.2.x series is current stable release. (while 1.3.x series does not have a label)
As you can see, it's difficult to find common rule what 'latest' should mean in Apache projects.
Considering the intention that we're not intentionally releasing 'unstable' version, i prefer 'latest / stable' tiny bit more than 'beta / stable'.
I'd like hear more opinions.
On Tue, Mar 21, 2017 at 9:16 AM Jan Rasehorn <[hidden email]> wrote:
Sorry for bringing up an older topic .. I agree "latest" / "stable" makes a lot of sense.
Also what was *not* discussed in this thread is release cadence target.
IMHO, 2-3 releases a year should give a quicker turnover to release latest fixes and improvements / quicker feedback from the users?
Would be great to see 0.8.0 release soon..
I see on github there were a lot of awesome additions/commits since the last release.
On Tue, Mar 21, 2017 at 10:57 AM, moon soo Lee <[hidden email]> wrote:
|Free forum by Nabble||Edit this page|