I think the release of Jenkins 3.x is very urgent. Let me put forward another very important reason: companies and users are abandoning Jenkins. Jenkins 2.x has a history of 5 years. In the past 5 years, Jenkins 2.x has many major features and incompatible modifications. The obsolescence, update, and requirements for higher versions of Jenkins core require constant upgrading of Jenkins and modification of the configuration. This is in the view of the end user (administrator) of Jenkins, but it is a toss in the view of the leader. Small versions usually mean small changes. For the leaders of Jenkins administrators, Jenkins 2.x is something that hasn't changed a lot for many years, but it requires labor-intensive maintenance and repeated exploration. The minor version upgrade hides the value of the new version of Jenkins! News organizations do not pay attention to minor version updates, and the leadership does not care about minor version updates. Only the Jenkins administrator knows what Jenkins has updated! Enterprises and users have begun to consider abandoning Jenkins! ! We need to let the outside know that Jenkins is undergoing major changes, not that it has not released a major version for 5 years.
在2020年12月3日星期四 UTC+8 上午2:02:20<Jesse Glick> 写道： > Interesting, first I had seen Revapi. Would be worth checking whether > it can replace japicmp in `jenkinsci/jenkins`, which I introduced as > part of JEP-227 but had to patch in order to properly handle > POM/classpath changes (and unfortunately that patch remains > unevaluated). > -- 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/9d0ad61c-e63e-47d5-9034-1b648e002198n%40googlegroups.com.
