On Tue, 2014-07-08 at 13:59 +0200, Bertrand Delacretaz wrote: > On Tue, Jul 8, 2014 at 9:13 AM, Robert Munteanu <[email protected]> wrote: > > On Mon, 2014-07-07 at 11:58 +0200, Bertrand Delacretaz wrote: > >>...if you can put it in > >> https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.0/ in a > >> way that doesn't disturb Eclipse that's probably best? > >> > >> And add a link to that file to the > >> http://apache.org/dist/sling/eclipse/1.0.0/index.html page with a > >> recommendation to build from source? > > > > Yes, I'll do both of the above, after we've clarified that indeed it's > > OK to upload the source bundle... > > If we didn't vote on that source bundle we need to do that, so its a > decision of the PMC to release it.
So what should the next step from me be? Upload the source bundle for 1.0.0 release and restart the 1.0.0 vote? Or rather take down the 1.0.0 release and start the 1.0.2 release vote? And what should the process be? Would it be acceptable from a release POV if I 1. Uploaded a source bundle in a staging repo, which can undergo the regular release process 2. Once the vote is successful, drop the staging repo ( since the source bundle is not a usable Maven artifact ) and upload the following artifacts to dist/release/sling/eclipse ( names shortened just for this email ) - 1.0.0/source-bundle-1.0.0.zip - 1.0.0/update-site-1.0.0.zip - 1.0.0/(all jars/xmls required for a p2 update site ) Thanks, Robert
