Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

2019-09-25 Thread Justin Mclean
Hi, > we use asc for signing and sha256 or 512 is common for checksum, I think. > This is used in many projects and should be fine and up to date. That correct but you also have sha1 and md5s. > @Justin Mclean or is there any official rule or policy about that? Yes see [1] note the "and SHOULD

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC5

2019-09-25 Thread Aaron Coburn
+1 I verified the signatures and hashes for API/Core and Extensions artifacts (Note: in the future, you don't need to include *all of* md5, sha1, sha256 and sha512; just including one of sha512 or sha256 will suffice) The core and ext code builds and all the tests pass. I have some downstream

[VOTE] Release of Apache Tamaya 0.4-incubating-RC5

2019-09-25 Thread Anatole Tresch
Hi, I was running the needed tasks to get the 0.4-incubating release of Tamaya out. The artifacts available via the Apache distribution repository [1] and also via Apache's Nexus [2]. The tag for this release candidate is available at [3] and [4]. It will be renamed once the vote passed. Please

[jira] [Commented] (TAMAYA-408) Release 0.4-incubating

2019-09-25 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/TAMAYA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937648#comment-16937648 ] ASF subversion and git services commented on TAMAYA-408: Commit

[jira] [Commented] (TAMAYA-408) Release 0.4-incubating

2019-09-25 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/TAMAYA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937647#comment-16937647 ] ASF subversion and git services commented on TAMAYA-408: Commit

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

2019-09-25 Thread Julian Feinauer
Hi, we use asc for signing and sha256 or 512 is common for checksum, I think. This is used in many projects and should be fine and up to date. @Justin Mclean or is there any official rule or policy about that? Julian Am 25.09.19, 12:49 schrieb "Anatole Tresch" : Found: - .asc

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

2019-09-25 Thread Anatole Tresch
Found: - .asc for a (ASCII-armored) PGP signature - .md5 for a MD5 checksum - .sha1 for a SHA-1 checksum - .sha256 for a SHA-256 checksum, will be added - .sha512 for a SHA-512 checksum, will be added Am Mi., 25. Sept. 2019 um 12:42 Uhr schrieb Anatole Tresch <

Re: [VOTE] Release of Apache Tamaya 0.4-incubating-RC4

2019-09-25 Thread Anatole Tresch
Does anybody see what are the correct hashes now needed? sha1 and md5 are still there in most projects in https://dist.apache.org/repos/dist/release Some also have sha512 which I can easily add, I think. What is the exact requirement? J Anatole

[RESULT][VOTE] Release of Apache Tamaya 0.4-incubating-RC4

2019-09-25 Thread Anatole Tresch
Since there are still minor issues with some checksums I close this vote with a NO result. Lets go for RC5 and keep fingers crossed! -- *Anatole Tresch* PPMC Member Apache Tamaya JCP Star Spec Lead *Switzerland, Europe Zurich, GMT+1* *maketechsimple.wordpress.com