On 2017-10-05 14:33, Ian Boston wrote:
Hi,
Currently the whole Oak source tree is synchronously versioned. Which is
great for Oak and its releases, but problematic downstream. I assume this
has been discussed before, and hope it can be discussed again ?
------
If it can, here is some supporting evidence, using Sling as an example.If
it cant be discussed and the case is closed, the please ignore this thread.
Currently:
When a version of Sling depends on Oak 1.6, 1.4 or 1.2 , and needs a
feature or an API from Oak 1.8-SNAPSHOT, that feature or API must be
backported and released to 1.6, 1.4 or 1.2, but probably all versions back
to the one desired.
...
Wait.
Why would a new release of Sling *ever* reference an Oak version older
than the latest stable version?
(I understand that this doesn't address the part about getting something
into the latest stable release, but AFAICT it simplifies your problem
statement).
Best regards, Julian
