Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
On Thu, Sep 16, 2010 at 6:23 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Thu, Sep 16, 2010 at 5:27 PM, Vidar Ramdal vi...@idium.no wrote: ... CHECK SIGNATURES AND DIGESTS sling-staging/039/.index/nexus-maven-repository-index.gz gpg: md5: BAD sha1: BAD Should be SLING-1780, can you svn up and try again? Thanks, that did it, so I'm happy to give my +1 -- Vidar S. Ramdal vi...@idium.no - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 22 00 84 76 Quando omni flunkus moritatus!
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
Felix Meschberger wrote +1 What sounds a bit odd, though, is the bundle symbolic names: org.apache.sling.jcr.jcrinstall org.apache.sling.osgi.installer org.apache.sling.install.fileinstall Sounds like they have something in common, but not really much ... Wouldn't it make sense to have some concise naming convention for this ? For example org.apache.sling.install.core (today: ...osgi.installer) org.apache.sling.install.provider.jcr (today: ...jcr.jcrinstall) org.apache.sling.install.provider.file (today: ...install.fileinstall) Hmm, yes I agree the symbolic names are a little mess :) Ok, the first question is: should we stop the vote? Once this is published it gets harder to change it. So, given that we have no release for several years of this stuff, it doesn't matter if it takes one or two weeks longer. I would suggest that we continue the vote for the testing bundle but stop for the installer stuff (not sure if it is possible to just promote a part of the staging repo) I would also like that the package names have something do to with the symbolic name. WDYT? Carsten -- Carsten Ziegeler cziege...@apache.org
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
On Fri, Sep 17, 2010 at 10:03 AM, Carsten Ziegeler cziege...@apache.org wrote: ...I would also like that the package names have something do to with the symbolic name Works for me - when I chose the original names I wanted to make it clear that the OSGi installer is not sling-specific, as opposed to the jcrinstall module. I agree with fixing the symbolic names before releasing, the names suggested by Felix look good to me. -Bertrand
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
Hi, Agreed with cancelling the vote with respect to the installer parts and continuing for the testing parts. As for repository.a.o: I think you have to drop the entire staging and then upload again. But since the vote has already passed (and trusting you to do the right thing) I would then assume the staging repository may immediately be released, maybe with a comment indicating the successful vote for this (such that we have it in the commit list archive). Regards Felix Am 17.09.2010 10:03, schrieb Carsten Ziegeler: Felix Meschberger wrote +1 What sounds a bit odd, though, is the bundle symbolic names: org.apache.sling.jcr.jcrinstall org.apache.sling.osgi.installer org.apache.sling.install.fileinstall Sounds like they have something in common, but not really much ... Wouldn't it make sense to have some concise naming convention for this ? For example org.apache.sling.install.core (today: ...osgi.installer) org.apache.sling.install.provider.jcr (today: ...jcr.jcrinstall) org.apache.sling.install.provider.file (today: ...install.fileinstall) Hmm, yes I agree the symbolic names are a little mess :) Ok, the first question is: should we stop the vote? Once this is published it gets harder to change it. So, given that we have no release for several years of this stuff, it doesn't matter if it takes one or two weeks longer. I would suggest that we continue the vote for the testing bundle but stop for the installer stuff (not sure if it is possible to just promote a part of the staging repo) I would also like that the package names have something do to with the symbolic name. WDYT? Carsten
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
Hi, I cancel hereby the vote for the OSGi Installer, JCR Installer, and File Installer - I already removed the artifacts from the staging repository (thanks to Nexus this is possible). We continue with the vote for Commons Testing of course. Thanks for your support! Carsten -- Carsten Ziegeler cziege...@apache.org
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
On Thu, Sep 16, 2010 at 9:48 AM, Carsten Ziegeler cziege...@apache.org wrote: Hi, as announced it's time for some more releases :) Apart from our first releases of OSGi Installer 3.0.0 JCR Installer 3.0.0 File Installer 1.0.0 I've added Commons Testing 2.0.6 (which is a dep of jcr installer) https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12310710fixfor=12314354 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-039/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 039 /tmp/sling-staging Don't know if this is just me, but I'm getting reports on bad signatures for all artifacts: CHECK SIGNATURES AND DIGESTS sling-staging/039/.index/nexus-maven-repository-index.gz gpg: md5: BAD sha1: BAD sling-staging/039/.index/nexus-maven-repository-index.properties gpg: md5: BAD sha1: BAD sling-staging/039/.meta/p2-metadata.properties gpg: md5: sha1: sling-staging/039/.meta/repository-metadata.xml gpg: md5: sha1: sling-staging/039/org/apache/sling/org.apache.sling.commons.testing/2.0.6/org.apache.sling.commons.testing-2.0.6-javadoc.jar gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.commons.testing/2.0.6/org.apache.sling.commons.testing-2.0.6-source-release.zip gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.commons.testing/2.0.6/org.apache.sling.commons.testing-2.0.6-sources.jar gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.commons.testing/2.0.6/org.apache.sling.commons.testing-2.0.6.jar gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.commons.testing/2.0.6/org.apache.sling.commons.testing-2.0.6.pom gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.commons.testing/maven-metadata.xml gpg: md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.install.fileinstall/1.0.0/org.apache.sling.install.fileinstall-1.0.0-source-release.zip gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.install.fileinstall/1.0.0/org.apache.sling.install.fileinstall-1.0.0-sources.jar gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.install.fileinstall/1.0.0/org.apache.sling.install.fileinstall-1.0.0.jar gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.install.fileinstall/1.0.0/org.apache.sling.install.fileinstall-1.0.0.pom gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.install.fileinstall/maven-metadata.xml gpg: md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.jcr.jcrinstall/3.0.0/org.apache.sling.jcr.jcrinstall-3.0.0-source-release.zip gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.jcr.jcrinstall/3.0.0/org.apache.sling.jcr.jcrinstall-3.0.0-sources.jar gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.jcr.jcrinstall/3.0.0/org.apache.sling.jcr.jcrinstall-3.0.0.jar gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.jcr.jcrinstall/3.0.0/org.apache.sling.jcr.jcrinstall-3.0.0.pom gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.jcr.jcrinstall/maven-metadata.xml gpg: md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.osgi.installer/3.0.0/org.apache.sling.osgi.installer-3.0.0-javadoc.jar gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.osgi.installer/3.0.0/org.apache.sling.osgi.installer-3.0.0-source-release.zip gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.osgi.installer/3.0.0/org.apache.sling.osgi.installer-3.0.0-sources.jar gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.osgi.installer/3.0.0/org.apache.sling.osgi.installer-3.0.0.jar gpg: BAD md5: BAD sha1: BAD sling-staging/039/org/apache/sling/org.apache.sling.osgi.installer/3.0.0/org.apache.sling.osgi.installer-3.0.0.pom gpg: BAD md5: BAD sha1:
RE: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
Don't know if this is just me, but I'm getting reports on bad signatures for all artifacts: i've tested it on a linux machine and got GOOD results for the md5 and sha1 hashes, BAD only for pgp (although i've scanned the results only briefly and deleted them already) stefan
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
On Thu, Sep 16, 2010 at 5:27 PM, Vidar Ramdal vi...@idium.no wrote: ... CHECK SIGNATURES AND DIGESTS sling-staging/039/.index/nexus-maven-repository-index.gz gpg: md5: BAD sha1: BAD Should be SLING-1780, can you svn up and try again? -Bertrand
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
On Thu, Sep 16, 2010 at 9:48 AM, Carsten Ziegeler cziege...@apache.org wrote: ...Apart from our first releases of OSGi Installer 3.0.0 JCR Installer 3.0.0 File Installer 1.0.0 I've added Commons Testing 2.0.6 (which is a dep of jcr installer) https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12310710fixfor=12314354... +1 to the release. Checked sigs and md5, and briefly tested OSGi Installer 3.0.0 and JCR Installer 3.0.0 on a complex $work project, looks good! -Bertrand
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
+1 What sounds a bit odd, though, is the bundle symbolic names: org.apache.sling.jcr.jcrinstall org.apache.sling.osgi.installer org.apache.sling.install.fileinstall Sounds like they have something in common, but not really much ... Wouldn't it make sense to have some concise naming convention for this ? For example org.apache.sling.install.core (today: ...osgi.installer) org.apache.sling.install.provider.jcr (today: ...jcr.jcrinstall) org.apache.sling.install.provider.file (today: ...install.fileinstall) WDYT ? Regards Felix Am 16.09.2010 09:48, schrieb Carsten Ziegeler: Hi, as announced it's time for some more releases :) Apart from our first releases of OSGi Installer 3.0.0 JCR Installer 3.0.0 File Installer 1.0.0 I've added Commons Testing 2.0.6 (which is a dep of jcr installer) https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12310710fixfor=12314354 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-039/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 039 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for 72 hours. Carsten
