The Apache process is that you vote for an RC, and if the vote passes (i.e. three +1 from PMC and no -1) the same artifacts will be released (without RC). If issues are discovered, there may be another RC.
Note that the RC is published on Jun's directory, not an official Kafka repository. You can see more details here: http://www.apache.org/dev/release-publishing http://www.apache.org/dev/release.html On Wed, Jan 14, 2015 at 9:12 AM, Stevo Slavić <ssla...@gmail.com> wrote: > Hello Apache Kafka community, > > Is currently active vote for 0.8.2.0-RC1 or 0.8.2.0? > > If the vote is for 0.8.2.0-RC1 why isn't that reflected in artifact > metadata? Version should be 0.8.2.0-RC1, 0.8.2-RC1 or something similar > (0.8.2 beta release had "-beta" and no ".0" suffix - see > http://repo1.maven.org/maven2/org/apache/kafka/kafka_2.10/0.8.2-beta/ ) > If it stays like this, and final gets released later with same 0.8.2.0 > version, but different content - repositories, both local and remote will > get polluted with junk. > > If the vote is for 0.8.2.0 final GA release, why call the vote candidate 1? > > Also, version related - none of the previous 0.8.x releases had ".0" > release i.e. 0.8.x.0. Is this change in version numbering intentional? > > Kind regards, > Stevo Slavic.
