My initial thought before writing this mail was to suggest two launchpads, one very minimal which we can release more frequently. This would contain the bare minimum and gets people playing around with it. And the other one would be the full blown thing used for testing. We could even add all modules to the full one.
Looking at the snapshot list of the builder project, I guess we could just release all of them and we're got with Sling 7 and then maybe have a look at how to change things after Sling 7? So if there are people interested in driving the release of the individual bundles, we should be done with that prett fast :) And I totally agree that the documentation needs to be updated, revised Carsten 2014-07-22 14:31 GMT+02:00 Daniel Klco <[email protected]>: > I agree with a release of 7 in general. I think we need to also as Oliver > indicated, create a release roadmap so we have some schedule in mind for > the future. > > On that note, what about increasing the frequency of Launchpad releases? > Right now releases are infrequent enough that it's a 'big deal' if a > dependency isn't ready, which may not be the case if the launchpad releases > we biannual or even quarterly. Also, the documentation for Sling 6 is > quite stale and does not include many important features which are used in > downstream applications. > > -Dan > > > On Tue, Jul 22, 2014 at 7:30 AM, Bertrand Delacretaz < > [email protected] > > wrote: > > > On Tue, Jul 22, 2014 at 12:20 PM, Oliver Lietz <[email protected]> > > wrote: > > > ...My goals for a first *Karaf* Launchpad release are a current > released > > JCR > > > Server (whether Jackrabbit or Oak) and getting the Event bundle fixed > > (not > > > sure what's the cause for a failing IT yet).... > > > > Are you planning to setup integration tests for that Karaf-based > launcher? > > > > If we can provide that (at http://ci.apache.org/ as well) it lets > > users decide which launcher they want to use, knowing that all our > > tests pass when that launcher is used. > > > > -Bertrand > > > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
