Hi All, I agree that we have to continue our code cleanup and optimization, but should not add breaking changes in our current major version. The best approach would be to start creating a technical debt or maybe a "migration guide" for our external developers. Once there is a 2.0 branch and there are builds they can start creating a 2.0 compatible version. All Major changes or updates to this guide/debt page should also be announced here on the developers list so they know their plugins could be impacted.
Cheers, Hans On Fri, 24 Sept 2021 at 11:03, Matt Casters <[email protected]> wrote: > Dear Hoppers, > > Nicolas just filed a great PR for an API simplification. I really like it > but at the same time we already have a number of plugins external to the > project and we probably don't want to break all that code. > Unfortunately this PR is not the last thing we'd want to change with the > upcoming Java 11 (and beyond) code migration is still ahead of us. So how > do we structurally tackle this? > > Creating a task in JIRA is one thing, perhaps we can document this as well > to make it easier to later migrate plugins to version 2 (and beyond)? > Should we start a "technical debt" page in the developer documentation? > > Cheers, > Matt > -- > Neo4j Chief Solutions Architect > *✉ *[email protected] >
