Thanks for heads up! Please consider updating versions in JIRA - 0.8.2 --> 0.8.2.0, and labeling 0.8.2.0 as released.
Kind regards, Stevo Slavic. On Wed, Jan 14, 2015 at 6:54 PM, Jun Rao <j...@confluent.io> wrote: > About the versioning, we had released 0.8.1 and 0.8.1.1 before, which is a > bit inconsistent in terms of versioning format. So picking 0.8.2.0 is > intended to fix that inconsistency. > > Thanks, > > Jun > > 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. > > >