Hi, The release process for the initial version of the Sling IDE Tooling was a bit rough. We discovered a few problems even after the release was completed. To sum up the discussions, we had
- an initial call for comments on the release process [1] - an initial release vote based on a source bundle [2] - a second release vote based on a staged Maven repository [3] The first release, based on a source bundle, was canceled because it was based on a SNAPSHOT version and was uploaded on a global public space ( https://dist.apache.org/repos/dist/dev/sling ) . The second release was approved but it was later found out that no source bundle was uploaded to https://dist.apache.org/repos/dist/sling [4]. Indeed, the Maven-based source artifacts can not be used to easily rebuild the final product. For the second release, I'd like to make this a bit smoother :-) . Therefore, I propose the following process: 1. Vote will be held on a source bundle which can be used to rebuild the product using mvn clean package 2. The source bundle ( jar file ) will be uploaded to repository.apache.org in a staging repo 3. Once the vote is passed the staging repo will be dropped ( not promoted ) as there is no sense to publish only a source bundle to Maven Central 4. The source bundle will be uploaded to https://dist.apache.org/repos/dist/sling/eclipse/$VERSION, together with two convenience binary sets - a zipped update site, to download for offline installation - an expanded update site, to install directly from Eclipse I'd appreciate any comments on this process as I plan to start a new release vote in a couple of days. Thanks, Robert [1]: http://sling-dev.markmail.org/thread/d2gmgsmwe4uhobsb [2]: http://sling-dev.markmail.org/thread/73vpkohly64mgm7m#query:+page:1+mid:epzey4nw2oklerti+state:results [3]: http://sling-dev.markmail.org/thread/s6xvoxqjcorc54cn [4]: http://sling-dev.markmail.org/thread/hgxbejjrmn4wrpsv
