Incremental changes are easier to manage and test and easier to back out.
3.7 Bug fixes and performance
3.8 Move to new layering. Owl will moves its usage of layering to new
layering and test it. If others are using layering, please chime in.
4.0 Move to new Scala version ...
Sincerely,
I'm agreeable with seeing 4.0.0 drop Java 8 support, bump to Scala 2.13, merge
sapi and japi into api, change directory / jar names, and remove deprecated
parts. I also don't think it's worth supporting both the old and new layer
APIs. I haven't developed any layer classes or schemas using
I think the compelling argument to get the layers stuff into 3.7.0 is that
we don't want any more layers built using 3.6.0-and-prior APIs.
I tend to agree we should not make the next release 4.0.0 because we have
other things to get into that release, and the layers stuff is not an
official part
I don't think we should make our next release 4.0.0. There's a handful of
changes that have been discussed that probably require a major version bump
(e.g. drop Java 8 support, bump to Scala 2.13, merge sapi and japi into api,
change directory structures/jar names, remove deprecated
