Hi Thomas, Guess it is always better to release the full project to avoid to manage a one time compatibility matrix which is always a hell for end users (and us).
Side note: if the jcache stuff is bothering you, feel free to start a thread to drop it, guess it was not adopted and due to impl divergences the original goal was reached in another apache project so if it is the main blocker for you I guess it can disappear soon. Best, Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mar. 7 nov. 2023 à 20:05, Thomas Vandahl <t...@apache.org> a écrit : > Hi folks, > > would it be considered good practice to release just one sub-component > (commons-jcs3-core) of the project to fix bugs? All other components are > unaffected. What would be the release artefact to vote on? Please advise. > > Bye, Thomas > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
