Hi Martin,
So I think the development branch, which was JDK8 before, could also be called geoapi-compatibility, or geoapi-latest. I think in the future if others ask about it, maybe just adding a note about it in the Developer Guide, or somewhere else in the site documentation, would be enough. Thanks for clarifying! Bruno ________________________________ From: Martin Desruisseaux <[email protected]> To: [email protected] Sent: Friday, 15 June 2018 1:38 AM Subject: Re: git push --force applied, next step proposal Hello Bruno Thanks for the feedback! Le 14/06/2018 à 14:50, Bruno P. Kinoshita a écrit : > Minor nit-pick, what's the rationale behind master & development? > The "development" branch uses GeoAPI methods or interfaces that are not yet in the official GeoAPI release. This serves two purposes: * Verify that the interfaces proposed for next GeoAPI releases work. * Be ready to upgrade easily to next GeoAPI versions after its release. But the Apache releases can not depend on a GeoAPI 4.0-SNAPSHOT. We need to downgrade to GeoAPI 3.0.1 (until a new GeoAPI release is available). This downgrade is applied on "master", which is the branch from which Apache SIS releases are made. The fact that "master" is more stable is just a side-effect of above, since "development" get the day-to-day commits and "master" only get the backports a few time per months. But we can try other development models too if there is proposal. Martin
