Oh, before I forget... the take 2 SCM tag was pushed to ASF git servers, so perhaps we should push the fa42b42 tag with a distinguishing tag name. Github seems to be smart enough to pick up that the tag changed: https://github.com/apache/maven-scm/tree/maven-scm-1.9 but others who checked out from GIT during the take 2 vote may not.
Oh also I forgot I had a 4th test which passes: * source release matches tag => PASS (only missing files are the generated DEPENDENCIES, NOTICE and LICENSE files, otherwise identical) On 8 January 2014 09:13, Stephen Connolly <stephen.alan.conno...@gmail.com>wrote: > Tests performed by me: > > * Source release SHA1 sum matches in email => PASS > * RAT report is same or better than previous release => 0 files, so PASS > * Source bundle builds successfully => PASS > > These are all the tests I have time to run right now, but on this basis I > am happy to vote > > +1 (binding) > > -Stephen > > > On 7 January 2014 18:22, domi <d...@fortysix.ch> wrote: > >> Hi, >> >> We fixed 11 issues. The new feature is the jgit provider (based on jgit). >> Details: >> >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&version=18783 >> >> Staging repository: >> https://repository.apache.org/content/repositories/maven-009/ >> >> Staged site: http://maven.apache.org/scm-archives/scm-LATEST/ >> >> Sources release: >> >> https://repository.apache.org/content/repositories/maven-009/org/apache/maven/scm/maven-scm/1.9/maven-scm-1.9-source-release.zip >> >> Source release checksum(s): >> maven-scm-1.9-source-release.zip sha1: >> e1e6323c43ba9ceaa4cb62d94b7cb9266c8f1897 >> Vote open for 72H >> >> [+1] >> [0] >> [-1] >> >> Thanks >> Dominik Bartholdi >> >> >
