RE: [VOTE] Release Apache Empire-db 2.0.5-incubating (rc5)
I have checked the release and I have found the following issues: - jar files in the maven2 repo and the distribution differ. No idea how this can happen. (see below)) - francis' signature is not in the KEYS.txt on the website. (see below)) Everything else looks good, except the issues sebb found. If these issues are fixed, an rc will get a +1 from me Thomas I have checked the following: staging repo: - empire-db - jar contains NOTICE and LICENSE -empire-db-struts2 - jar contains NOTICE and LICENSE -empire-db-example-advanced - jar contains NOTICE and LICENSE -empire-db-example-basic - jar contains NOTICE and LICENSE -empire-db-example-cxf - jar contains NOTICE and LICENSE rat report looks good distribution: - NOTICE, LICENSE and DISCLAIMER look good - javadoc looks good - sources look good - sources build - unit tests pass - all required dependencies are available from central repository, - docs (README.txt, tutorial.pdf) look good - md5 and sha1 sums are correct - signatures are correct, however, francis' key is not in the KEYS.txt. This needs to be fixed. compare maven repo and distribution: - empire-db-2.0.5-incubating.jar in staging repo and in zip/tgz differ binaryly. The file size in the staging repository is 269.663 bytes, whereas in the sistribution, it is 269.664 bytes. empire-db-struts2-2.0.5-incubating.jar also seems to be different, but has same file size. Regards, Thomas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release PhotArk M1-incubating (RC4a)
The PhotArk community has completed a vote on it's first milestone release (PhotArk M1-Incubating) and is now looking for IPMC approval to publish the release. Please review and vote on approving the M1-incubating release artifacts of PhotArk. The artifacts are available for review at: http://people.apache.org/~lresende/photark/M1-incubating-RC4a/ This includes the signed binary and source distributions, the RAT report, and the Maven staging repository. The release tag is available at : https://svn.apache.org/repos/asf/incubator/photark/tags/M1-incubating-RC4a/ The vote thread from PhotArk dev list: http://www.mail-archive.com/photark-...@incubator.apache.org/msg00150.html Previous release candidate review in general list http://www.mail-archive.com/general@incubator.apache.org/msg21108.html -- Luciano Resende http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Empire-db 2.0.5-incubating (rc5)
The jar diff is discussed in an other thread. Added myself to the site: http://incubator.apache.org/empire-db/community/contributors.htm meanwhile I created this document on the wiki: http://cwiki.apache.org/confluence/display/empiredb/Becoming+part+of+the+team (just as a start) the keys on the website points to http://www.apache.org/dist/incubator/empire-db/KEYS I suggest it points to a location in the repo where it is kept so we don't have to update two copies each time. We should at least update the dist/incubator/empire-db/KEYS file when the release is accepted (if we keep it) I added myself a while ago to the keys in our repo/trunk/tools/KEYS.txt. Should we move that file to trunk and publish it in the dist? also from here: http://incubator.apache.org/guides/releasemanagement.html#distribution-checksums-sigs that the KEYS file contains the public key. (Storing public keys in a KEYS file is recommended but is not policy.) further my public key is available here: http://pgp.mit.edu:11371/pks/lookup?search=francisdb Cheers, Francis On Sun, Sep 13, 2009 at 1:20 PM, Thomas Fischer fisc...@seitenbau.net wrote: I have checked the release and I have found the following issues: - jar files in the maven2 repo and the distribution differ. No idea how this can happen. (see below)) - francis' signature is not in the KEYS.txt on the website. (see below)) Everything else looks good, except the issues sebb found. If these issues are fixed, an rc will get a +1 from me Thomas I have checked the following: staging repo: - empire-db - jar contains NOTICE and LICENSE -empire-db-struts2 - jar contains NOTICE and LICENSE -empire-db-example-advanced - jar contains NOTICE and LICENSE -empire-db-example-basic - jar contains NOTICE and LICENSE -empire-db-example-cxf - jar contains NOTICE and LICENSE rat report looks good distribution: - NOTICE, LICENSE and DISCLAIMER look good - javadoc looks good - sources look good - sources build - unit tests pass - all required dependencies are available from central repository, - docs (README.txt, tutorial.pdf) look good - md5 and sha1 sums are correct - signatures are correct, however, francis' key is not in the KEYS.txt. This needs to be fixed. compare maven repo and distribution: - empire-db-2.0.5-incubating.jar in staging repo and in zip/tgz differ binaryly. The file size in the staging repository is 269.663 bytes, whereas in the sistribution, it is 269.664 bytes. empire-db-struts2-2.0.5-incubating.jar also seems to be different, but has same file size. Regards, Thomas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.somatik.be Microsoft gives you windows, Linux gives you the whole house. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Empire-db 2.0.5-incubating (rc5)
On Sun, Sep 13, 2009 at 7:38 PM, Francis De Brabandere franci...@gmail.com wrote: I added myself a while ago to the keys in our repo/trunk/tools/KEYS.txt. Should we move that file to trunk and publish it in the dist? I would say so. The advantage of having the KEYS file also in the /dist/ is that it'll be close to where its used. The advantage of SVN, well that should be obvious :) also from here: http://incubator.apache.org/guides/releasemanagement.html#distribution-checksums-sigs that the KEYS file contains the public key. (Storing public keys in a KEYS file is recommended but is not policy.) further my public key is available here: http://pgp.mit.edu:11371/pks/lookup?search=francisdb Yeah, publishing a KEYS file by itself does not really provide the end user with much additional guarantee beyond a SHA1 hash of the file (which is why imagine KEYS files are not policy). The thing that matters much more is linking up to the apache web of trust: http://www.apache.org/dev/release-signing.html#web-of-trust For similar reasons it is also good if multiple people sign releases - more trust :) cheers, - Leo (who in java land already considers it a win these days when people opt out of auto-downloading from ibiblio.org, so personally no longer bothers with GPG) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Empire-db 2.0.5-incubating (rc5)
Francis De Brabandere franci...@gmail.com schrieb am 13.09.2009 20:38:26: ... the keys on the website points to http://www.apache.org/dist/incubator/empire-db/KEYS I suggest it points to a location in the repo where it is kept so we don't have to update two copies each time. I am not sure this is feasible. Locating it in the dist site seems standard to me, though I do not know whether it is an absolute must. If there is no compelling reason to move it, please keep the file there, but make sure your public key is contained in it. We should at least update the dist/incubator/empire-db/KEYS file when the release is accepted (if we keep it) Francis, you can simply add your key, no matter whether the release is accepted or not, and preferably before the release is voted on. It is no problem if there is no release for a key in the KEYS file. I added myself a while ago to the keys in our repo/trunk/tools/KEYS.txt. Should we move that file to trunk and publish it in the dist? I'm not sure whether I understand you correctly, but the file repo/trunk/tools/KEYS.txt is fine as KEYS file. Just make sure the file in the dist directory has the same content. ... further my public key is available here: http://pgp.mit.edu:11371/pks/lookup?search=francisdb Yes, I checked that. But everybody can upload keys to a keyserver and call themselves Francis De Brabandere, so this is no real protection, just convenience. Thomas On Sun, Sep 13, 2009 at 1:20 PM, Thomas Fischer fisc...@seitenbau.net wrote: I have checked the release and I have found the following issues: ... - francis' signature is not in the KEYS.txt on the website. (see below)) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
