On 22/12/2012, at 9:46 AM, Olivier Lamy <ol...@apache.org> wrote: > 2012/12/21 Benson Margulies <bimargul...@gmail.com>: >> Dear fellow community members, >> >> Discussions today have made it clear, to me at least, that we're >> missing a step in the release procedures for plugins and component >> (indeed, for everything except 'core' releases). >> >> The step is to copy the official release package (the source-release >> artifact) to the Apache dist hierarchy, in some fashion compatible >> with svnpubsub. >> > funny to have to put a source-relase for a pom .... > Does it mean all artifacts deployed to maven central need to have a > source-release in /dist ? > Only source-release or more ? (fun to have those duplicate in my local > maven repo and in the directory I will use to checkout this /dist)
I think the source release would suffice (and we don't necessarily need to push that to r.a.o if it's not useful). For the POM, I'd say we can probably just push the file itself. > > How other ASF projects will do ? Yes Benson this doesn't concern only > Maven plugins etc... > I think about some which produce osgi bundle from other projects > (sample > http://repo.maven.apache.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.commons-io/1.4_3/ > so all those bundles need to be /dist or this one > http://repo.maven.apache.org/maven2/org/apache/directory/studio/org.apache.commons.lang/2.6/ > ) > Do they need to do it too ? http://sling.apache.org/site/release-management.html#ReleaseManagement-PromotingtheRelease - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
