Hi, Anataloe thanks for your steady work!
Am 05.04.2016 um 21:49 schrieb Anatole Tresch: > > ------------------------------------------------ > [ ] +1 for community members who have reviewed the bits > [ ] +0 > [ ] -1 for fatal flaws that should cause these bits not to be > released, and why.............. > ------------------------------------------------ MD5HASHES While clicking through the artifacts I wasn't able to verify the md5sums: $ md5sum apache-tamaya-0.2-incubating-distribution-src.tar.gz 3d6f68a118d792bd4fbbcbb5af7893bb apache-tamaya-0.2-incubating-distribution-src.tar.gz $ wget https://dist.apache.org/repos/dist/dev/incubator/tamaya/0.2-incubating/apache-tamaya-0.2-incubating-distribution-src.tar.gz.md5 $ cat apache-tamaya-0.2-incubating-distribution-src.tar.gz.md5 a6d1ec4ae240f963c6f68e20e8385675 How were these files generated? Am I doing sth. wrong? Same goes for the binary artifact. SRC-ARTIFACT When I unpacked above artifact I found multiple pom.xml.releaseBackup - should we remove theses files or add it to gitignore? RELEASE-DOCS I assume we should use an example key/password in the documentation on howto perform a release - /docs/release-guide.html Most probably this would lead to a -1 if I were a member of the PMC. I do really like the documentation - in contrast to other projects it seems really useful to me. Cheers & sorry, Phil
signature.asc
Description: OpenPGP digital signature
