2009/4/23 David Jencks <[email protected]> > -1 (non binding) > > maven is working on releasing an apache pom 6 that includes the recommended > release profile. I'd wait a couple days for that. >
Hi David, that release is still being voted on - I've looked at the changes wrt. 5 and there is nothing really there that we need to pick up - it might mean we can remove a few definitions, but nothing (imho) worth waiting for, especially as we have some critical-fix releases waiting for the new Felix parent pom > Also I'm not sure why there are zips and tars, I'd expect only the pom to > be released. > this is a side-effect of the Felix release profile - it always creates two assemblies when packaging up a release (one of the binaries, one of the project) which are used as the main distribution files on http://felix.apache.org/site/downloads.cgi (this is the primary location for Apache Felix releases) these assemblies must be attached to the project so they will get signed by the maven-gpg-plugin, and md5/sha1 digests will be created when we deploy them in the past the Felix release process was manual - so the deploy would be done to a local directory where the release manager could remove spurious assemblies (like *.bz2, or the project/binary ones for the Felix parent pom) before starting the vote and finally uploading Maven artifacts to 'central', and the assemblies to 'dist' ( though sometimes people would copy all files to 'central' including the bz2 ones ) now that we're using Nexus to stage the deployed release you can see the attached assemblies, because all attached artifacts get sent via Nexus - I managed to remove the unnecessary *.bz2 files by using the build-helper-plugin, but we still need to have the project and binary assemblies there for a) signatures+digests and b) voting so this really is "business-as-usual", it's just that previously we were able to tweak things so you didn't see assemblies for the parent pom, but they were always there (perhaps in the future we'll be able to filter out these files again during deploy/staging) HTH thanks > david jencks > > > On Apr 22, 2009, at 10:22 AM, Stuart McCulloch wrote: > > Hi, >> >> I've finally put together release 1.2.0 of the Felix parent pom - this >> uses >> the new >> Nexus repository infrastructure to stage releases. I've also changed the >> artifactId >> to be "felix-parent", which should be less confusing for people browsing >> the >> repo. >> >> The release is staged at: >> >> https://repository.apache.org/content/repositories/felix-staging-015/ >> >> The new release process is documented on the wiki (based on the Maven >> process): >> >> >> >> http://cwiki.apache.org/confluence/display/FELIX/Release+Management+(Nexus)<http://cwiki.apache.org/confluence/display/FELIX/Release+Management+%28Nexus%29> >> >> You can use this UNIX script to download the release and verify the >> signatures: >> >> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh >> >> Usage: sh check_staged_release.sh 015 /tmp/felix-staging >> >> Please vote to approve this release: >> >> [ ] +1 Approve the release >> [ ] -1 Veto the release (please provide specific comments) >> >> This vote will be open for 72 hours ... I'm off to get some sleep now, >> back >> in ~8hrs. >> >> -- >> Cheers, Stuart >> > > -- Cheers, Stuart
