I'm not sure "strict semver" can be automated: functional change can't be easily detected if there is no API change
semver is a great buzzword, but we should try to explain more precisely what can be automated in the plugin to try to follow the buzzword Regards, Hervé Le samedi 31 octobre 2015 12:14:09 Uwe Barthel a écrit : > Hi, > > I’m with Jason to move Maven forward to use (strict) semver as default > version strategy. > > I understand the 'cloudbee' strategy as a more exotic way. > But I'm interested in more than one strategy, configurable via plugin or > providing by default plugin. > > mit freundlichen Grüßen > Uwe Barthel --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
