The versioning seems fishy within https://dist.apache.org/repos/dist/dev/sling <https://dist.apache.org/repos/dist/dev/sling>. It contains org.apache.sling.ide.source-bundle-1.2.0.zip <https://dist.apache.org/repos/dist/dev/sling/ide-tooling-1.2.0/org.apache.sling.ide.source-bundle-1.2.0.zip> and org.apache.sling.ide.p2update-1.0.2.zip <https://dist.apache.org/repos/dist/dev/sling/ide-tooling-1.2.0/org.apache.sling.ide.p2update-1.0.2.zip> I guess the version number of p2update is wrong. Does that contain the full build p2repo? Would testing make more sense based on that? Does that include already the signed plugins?
Konrad > On 17. Jan 2018, at 22:38, Robert Munteanu <romb...@apache.org> wrote: > > Hi, > > We solved 30 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12334907 > > There are still some outstanding issues: > https://issues.apache.org/jira/browse/SLING/component/12320908 > > The release candidate has been uploaded at > https://dist.apache.org/repos/dist/dev/sling, The release artifact is > the source bundle - org.apache.sling.ide.source-bundle-1.2.0.zip - > which can be used to build the project using > > mvn clean package > > The resulting binaries can be installed into an Eclipse instance from > the update site which is found at p2update/target/repository after > building the project. > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/sling/trunk/tooling/ide/check_staged_re > lease.sh > > Usage: > sh check_staged_release.sh 1.2.0 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours > > Thanks, > > Robert
