Hi Michael, On 28/07/16 10:54, "Michael Marth" <[email protected]> wrote:
>I think we should simply stick to SemVer of the released artefacts to >signal those changes to upstream. IIUC the difference would be that one version (eg oak 1.6) could contain multiple compatibility versions (eg 1.2/1.4) - some perhaps marked as deprecated - while as using SemVer you'd have to have multiple versions of oak concurrently in an OSGi stack (which is likely not going to work) to achieve the same. Compatibility levels would be more flexible than SemVer. >On the more specific topic of session behaviour: could we use session >attributes to let the app specify session behaviour? [1] Yes, that would work too. >[1] >https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/S >ession.html#getAttribute(java.lang.String) Cheers, Stefan
