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]
