On Wednesday 23 July 2014 08:04:00 Carsten Ziegeler wrote: > 2014-07-22 23:12 GMT+02:00 Oliver Lietz <apa...@oliverlietz.de>: > > > +1, I think it's important to have a Sling 7 release soon. > > > > Yes, but not a half-baked one. We would have even more users complainig > > about > > 7 as we now have with 6. > > Well, which part do you think would be half-baked if we simply release > everything as is. I think most of the bundles (if not all) are in a pretty > good shape right now.
Sorry if it sounded to harsh. Some points which come to my mind: - we don't have full support for Java 8 - SLING-3575 failing test with newer Jackrabbit - the versions of Commons Threads for the Event bundle used at compile and runtime are not compatible - SLING-3008 looks still problematic - lack of documentation, major changes between 6 and 7, upgrade paths - Oak integration not on par with Jackrabbit (failing tests) I don't see any real value in releasing a *major* 7 now "as is" and then plan any future releases and how to improve the release process. If it takes even more time to get a major release out which can be used as good basis for future releases than so it be even if it takes more weeks or months. If the effort for releasing major versions is to high we should maybe switch to a rolling release model where we maintain a list with released and compatible bundles. Regards, O. > Carsten > > > >> I haven't checked the SNAPSHOT bundles, but I think there are some > > > > bundles > > > > >> where nothing changed after their latest release so we may use some > > >> already released bundles and not release *all* now. > > > > there are probaly less than 20 bundles. > > In theory, the list.xml should only reference snapshots which have actually > changes. But I'll check this today to see where we are. > > Carsten
