And after three weeks more - the oak.server bundle is the only one left with a SNAPSHOT version - we have a release in process for org.apache.sling.scripting.java 2.0.12 which looks important
I think it's a good idea to wait for that release to be done ( earliest on Monday afternoon ) and then remove oak + the two run modes from the launchpad and starting the release process for the 7 version. Thoughts? Are we still missing something for the 7 release? Robert On Wed, Sep 3, 2014 at 4:31 PM, Robert Munteanu <[email protected]> wrote: > Just as a follow-up three weeks later > > - the build works fine with Java 8 ( as a matter of fact, all > sling-trunk builds now pass ) > - there are 15 SNAPSHOT bundles referenced in the launchpad > - we decided to remove Oak support ( 1 SNAPSHOT bundle less ) , > tracked under [1] > - the oak support task is the only one blocking the 'release task' [2] > > So the work to be done is releasing those bundles and removing Oak support. > > If there's additional work to be done, please file new bugs blocking > [2] . And help with releasing bundles is always appreciated :-) > > Robert > > > [1]: https://issues.apache.org/jira/browse/SLING-3907 > [2]: https://issues.apache.org/jira/browse/SLING-3810 > > On Tue, Aug 5, 2014 at 10:09 AM, Bertrand Delacretaz > <[email protected]> wrote: >> Hi Oliver, >> >> On Tue, Aug 5, 2014 at 8:57 AM, Oliver Lietz <[email protected]> wrote: >>> ...https://github.com/oliverlietz/sling-tests >>> >>> Was an easier and faster way for me to create tests with Pax Exam and Karaf >>> instead of learning the Sling test stuff spread in different bundles in the >>> repo. Should be easy for me to recreate them in launchpad/integration-tests >>> when I'm done with SLING-3821.... >> >> Ok, fair enough - what's important IMO is to run the exact same >> integration tests suite in all environments, that is >> launchpad/integration-tests. Note that those require the >> launchpad/test-services bundle. >> >> -Bertrand
