Thanks for the typo in NEWS and CHANGES file. Those have both been fixed. I would tend to say that such minor typo should probably not trigger a re-roll, but since it appears no-one is willing to vote on this, maybe people expect a re-roll after all ?
PS: Yatong Zhang: this issue is not resolved. The 'fix version' on issue not resolved has no more meaning than "the version in which the ticket will be released *if* the issue is resolved by the time the release is voted on". On Tue, May 6, 2014 at 5:50 PM, Yatong Zhang <bluefl...@gmail.com> wrote: > and what about https://issues.apache.org/jira/browse/CASSANDRA-6092 ? It's > supposed to be fixed in 2.0.8 > > > On Tue, May 6, 2014 at 11:14 PM, Blair Zajac <bl...@orcaware.com> wrote: > > > In NEWS.txt the second 2.0.8 should be an earlier version. > > > > 2.0.8 > > ===== > > ... > > Upgrading > > --------- > > - Nothing specific to this release, but please see 2.0.8 if you are > > upgrading > > from a previous version. > > > > > > Blair > > > > On May 6, 2014, at 2:12 AM, Sylvain Lebresne <sylv...@datastax.com> > wrote: > > > > > Since a fair amount of bug fixes have been committed since 2.0.7 I > > propose > > > the > > > following artifacts for release as 2.0.8. > > > > > > sha1: 7dbbe9233ce83c2a473ba2510c827a661de99400 > > > Git: > > > > > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.8-tentative > > > Artifacts: > > > > > > https://repository.apache.org/content/repositories/orgapachecassandra-1011/org/apache/cassandra/apache-cassandra/2.0.8/ > > > Staging repository: > > > > > > https://repository.apache.org/content/repositories/orgapachecassandra-1011/ > > > > > > The artifacts as well as the debian package are also available here: > > > http://people.apache.org/~slebresne/ > > > > > > The vote will be open for 72 hours (longer if needed). > > > > > > [1]: http://goo.gl/G3O7pF (CHANGES.txt) > > > [2]: http://goo.gl/xBvQJU (NEWS.txt) > > > > >
