Hi, Thank you for the clarification. It sounds like Sling can't safely bind to 1.7.x and safely make releases that will not cause problems with package versions later. That blocks Sling from binding to any features not backported to a stable version of Oak.
The (obvious) reason for asking was I still need to get OAK-6575 into Sling. Since that wont be possible til 1.8 is released could the 1.6 backport patch I did for 1.6 be reconsidered ? Best Regards Ian On 13 October 2017 at 15:53, Angela Schreiber <[email protected]> wrote: > hi ian > > q1: i'd say no. but might require more rounds as we complete the m12n. > q2: yes. that's my understanding of the discussed we had just this week. > > one additional thing i would like to bring up: > IMHO we should consider making this an 2.0 release given the fact that the > m12n task is quite an effort. will send a separate email to get the > discussion started. > > kind regards > angela > > On 13/10/17 15:48, "Ian Boston" <[email protected]> wrote: > > >Hi, > >I have ported Sling to depend on Oak 1.7.8, and now that 1.7.9 is released > >I am updating the patch to port, finding 2 new bundles that were not > >required to make Sling build with Oak 1.7.8. > > > >oak-store-document > >oak-security-spi > > > >Is it too soon for Sling to depend on Oak 1.7.x ? > >Is there more modularisation to come before 1.8.0 is released ? > > > >Best Regards > >Ian > >
