> I'd like to see us start the Sling 6 release train soon, even if we > haven't nailed down the final Launchpad contents (chiefly the > discussion > about httpauth vs. formauth needs to be nailed down). > > IMHO, we need to start with API 2.1.0. Looking at JIRA, there > are just a > few outstanding issues: > > Issues which appear to resolved: > SLING-1566 - adding ResourceResolver.isLive() > SLING-1262 - implementing ResourceResolverFactory > > Issues for which patches are available: > SLING-1575 - moving auth API to Sling API (Felix to apply?) > SLING-1521 - removing license header from HtmlResponse (is the RAT > exclusion OK?) > > Assuming these can be resolved, that only leaves SLING-1193 > as targetted > at API 2.1.0 and not resolved. > > Justin
As discussed at [1] we should include the decoupling of the authentication mechanism from the JCR, which I know filed as a new issue under [2]. Because we're changing the API with SLING-1575 I think we should come up with a new API which solves all the known issues. Otherwise we're forced to change the API once again the next release which can turn into work for users of Sling. WDYT? best regards mike [1] http://markmail.org/message/aovh7lll4w6uwepv [2] https://issues.apache.org/jira/browse/SLING-1593
