-0: Hmmmm.... may have to rework somewhat the pom generation now that moved to GIT...
e.g. see https://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/cassandra-parent/1.0.7/cassandra-parent-1.0.7.pom at XPath /project/scm Those are SVN urls... should be git urls... I don't see this as blocking this release, but if somebody can create a JIRA for me I'll find some time to fix the URL generation... or maybe we just remove the url generation altogether as being GIT, the GIT urls don't include a branch details so the URL could just be static... but in any case this is POMs so I'd prefer if I sort it out. -Stephen On 12 January 2012 11:36, Sylvain Lebresne <sylv...@datastax.com> wrote: > It's a new year, quite a bunch of fixes since 1.0.6, feels like it's time to > do a new release. I thus propose the following artifacts for release as 1.0.7. > > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.0.7-tentative > Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/apache-cassandra/1.0.7/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-057/ > > The artifacts as well as the debian package are also available here: > http://people.apache.org/~slebresne/ > > Note that I had to adapt a little bit to the switch to git. In particular, > instead of using sha1 to mark the tentative commit of a release, I've decided > to use a lightweight tag, namely 1.0.7-tentative. My goal being that once the > vote passes, I'll delete this temporary tag and create the actual > cassandra-1.0.7 tag. My rational for not creating the final tag right away is > that: > - I want it to be clear 1.0.7 is not yet released > - If the vote fails, we would have to delete the tag anyway > If someone has a problem with that, let me know. > > The vote will be open for 72 hours (longer if needed). > > [1]: http://goo.gl/UTfwn (CHANGES.txt) > [2]: http://goo.gl/EHlRp (NEWS.txt)
