Hi. On Wed, 26 Dec 2018 20:41:59 +0700, Maxim Solodovnik wrote:
This is a [VOTE] for releasing Apache Commons collections 4.3 Tag name: collections-4.3-RC2 (signature can be checked from git using 'git tag -v')
$ git tag -v collections-4.3-RC2 error: tag 'collections-4.3-RC2' not found. Although I see it in the link below... What is going on?
RC1 was cancelled due to some release steps were not done Tag URL: https://gitbox.apache.org/repos/asf?p=commons-collections.git;a=commit;h=77e37dbf238d26351edb29e95391e3df75095d01 Commit ID the tag points at: 77e37dbf238d26351edb29e95391e3df75095d01 Site: https://dist.apache.org/repos/dist/dev/commons/collections/4.3-RC2/site/index.html
The Clirr report is still a problem:https://dist.apache.org/repos/dist/dev/commons/collections/4.3-RC2/site/clirr-report.html
[The same errors are reported on my machine, so it's not a cache issue...] Regards, Gilles
Distribution files (committed at revision 31689): https://dist.apache.org/repos/dist/dev/commons/collections/ Distribution files hashes (SHA256): commons-collections4-4.3-bin.tar.gz 214c12fae27403f1a16ca6c108b5a8682be1a885a0dbbfc8eb30941303e1fe94 commons-collections4-4.3-bin.zip 75b51a98fea6fca3746a3f70c6a0be24c99849e4976c4649214eaa5a009d0aeb commons-collections4-4.3-src.tar.gz 399f403feca86dbba7c4162eb90174db45979a2f7db2b3e0ba48240dc43ab434 commons-collections4-4.3-src.zip 1c637e260b5b9e372d196593c7617ad3adedb6da3ac9196d086f9fc24401f5c3 KEYS file to check signatures: https://www.apache.org/dist/commons/KEYS Maven artifacts:https://repository.apache.org/content/repositories/orgapachecommons-1405/Please select one of the following options: [ ] +1 Release it. [ ] +0 Go ahead; I don't care. [ ] -0 There are a few minor glitches: ... [ ] -1 No, do not release it because ...This vote will be open for at least 72 hours, i.e. until 2018-12-29T14:00:00Z(this is UTC time).
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx