Both of those (#622 and #630) look like important changes to merge. Getting the caching extension used and those interfaces exercised by the community is only a good thing.
Given there’s only one extension in that area right now, even if the extension point interfaces had to change to accommodate improvements over time it’s not the end of the world. Not sure there’s a convention here for marking interfaces as provisional, but it’s not unforeseeable that you'd want to change the signature of the extension point which will render newer versions of the extension unusable with older versions of Maven. I don’t think there’s anything wrong with that while it’s evolving. I think it’s more important to get the implementation used. If there’s an easy to let users know compatibility constraints are not set in stone yet then all the better. jvz > On Dec 13, 2021, at 5:39 AM, Guillaume Nodet <gno...@apache.org> wrote: > > In order to progress on a few issues, I'd like to discuss two points. > * merge https://github.com/apache/maven/pull/628 into the 3.8.x branch > and release 3.8.5 asap. This is a long-standing issue which had a couple > of trial fixes over the past months. > * create a 3.9.x branch to merge https://github.com/apache/maven/pull/630 > and https://github.com/apache/maven/pull/630 > > The 3.9.x will be needed in order to progress on > maven-build-cache-extension. Right now, the tests are done on two branches > that have to be built (for 3.x and 4.x), forbidding any kind of release > (which I don't propose at this time, we first need to extract it to a > separate repo anyway...) > > Thoughts ? > > -- > ------------------------ > Guillaume Nodet --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
