I am a user of both Jenkins CloudBees an OSS version. In the last months,
the Jenkins plugins version scheme changed for a few plugins and the
experience for Jenkins maintainers to update these plugin with confidence
regressed.
With the new CD workflow, the version change to `{digit}.{hash}` basically
telling us that every new version is a major bump and should be treated
like a breaking change. With such a vast plugin ecosystem and deployment
that contains 150+ plugins, it is a headache and error-prone experience to
bump the versions and read every "changelog".
I am not opposed to the continuous delivery and automatic release of every
commit, I am a big advocate to that approach in OSS and closed-source
software, however, I think the new jenkins version number is problematic
and CD should be implemented with a version number such as
SemVer https://semver.org/
I
created https://github.com/jenkins-infra/jenkins-maven-cd-action/issues/19
for the issue, but I think a better place should exist to discuss JEP-229.
--
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/6c870d41-9754-4e14-81d5-b9ff631fde78n%40googlegroups.com.
