> > Well, most Jenkins modules do not use semantic versioning ( > https://semver.org > <https://www.google.com/url?q=https%3A%2F%2Fsemver.org&sa=D&sntz=1&usg=AFQjCNG7RDMVbQiZzgQajrw0FRQab_ZC9Q>), > > but I think it is kind of common sense that you should not just increase > the patch level when you introduce incompatible changes. Plugins that > provide some kind of API should indicate changes in the API by increasing > the major version, i.e. in your case creating a 4.0.0 release. >
> Moving classes in an API module is something that should be done only if > you have no other chance to bring something forward. Is this the case in > your plugin? Is there no way to introduce a new API and keep the old API > alive? There are several alternatives available to improve an existing API. > The thing is, docker-java-api-plugin is just a wrapper. I'm not the maintainer of the underlying lib docker-java. If maintainers of docker-java don't conform to semver, I can't do anything about it. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3e9a8620-76c3-4329-af52-0529377a31ff%40googlegroups.com.
