Hi, On 20.08.2010 16:35, Justin Edelson wrote: > I can take JCR (which I'll probably split into two), Misc and possibly > Launchpad, although I'd prefer to push the Launchpad releases as late as > possible to see if we can do this installer/config admin stuff.
Ok. Agreed. That reminds me, that the OSGi Installer module is missing from the Sling 6 module list. Do we want to include JCR Install as well ? > > Is there a reason jcr.resource isn't part of the JCR batch? Not a strong one. I thougt it would make to release this together with the FS and Bundle Resource provider. Feel free to move ;-) > > Also... I never really built of jcr.webconsole, so I'm not sure this > should be released or included in the Sling 6 release. Right now, it's > just the NamespaceConfigurationPrinter. I would like to do more here, > but it's frankly not been a high priority. Ok, lets leave this out for the moment. > > commons.json doesn't need a release. The changes made since the last > release were all rolled back (actually, rolled into extensions.groovy). Ok, lets drop this again. Will you update the Wiki page accordingly ? Thanks. Regards Felix > > Justin > > On 8/20/10 10:23 AM, Felix Meschberger wrote: >> Hi all, >> >> I drafted a release plan for Sling 6 at [1]. >> >> I think it would be easiest if we collect the upcoming releases in >> batches. Once all Sling modules have been release, we will then be ready >> to do the Sling 6 release. >> >> Does this make sense or should something be changed ? >> Volounteers as release managers ? >> (Justin can you do the JCR Bundles release batch ?) >> Other comments ? >> >> >> Thanks and Regards >> Felix >> >> [1] >> https://cwiki.apache.org/confluence/display/SLING/Towards+Sling+6#TowardsSling6-ApacheSlingReleasePlan > >
