Hello Few points
> Marketing Definitely value in considering this, a 3.x and a big marketing push could bring some good attention to Jenkins, but do we have enough big changes to justify, possibly if we consider not just this LTS but other changes since 2.x. Some other stories worth highlighting: * GitHub checks integrations * Plugin site new features, release notes, issues, and coming soon a report a bug link taking you to creating an issue for the plugin * Read only Jenkins * UX modernisation * Couple of pluggable storage stories made some progress: test results and fingerprints > Date based I support this, we'll never have a problem with hitting a .300 'minor version' if we do this. @Olblak <m...@olblak.com> any thoughts on the effort involved here in release automation? > Number of breaking changes in weekly I agree we could bump to 3.x to signal a higher upgrade risk, but agree with others that the changes aren't too 'flashy'. I like Felix's idea of doing some bigger UX re-work for a 3.x, but I'm not sure we have enough contributors working in this area or time (assuming the next LTS), given that the next LTS selection is starting now. Thanks Tim On Tue, 26 Jan 2021 at 20:43, James Nord <te...@teilo.net> wrote: > > We do not have a fresh new massive story to share. At the same time > there could be a few changes to highlight: > > - Adoption of Configuration-as-Code as a recommended way to manage > Jenkins. > - Making emphasis on Jenkins-in-the-cloud applications and packaging, > with making Docker/Helm/etc. and downstream projects being promoted as > first class citizens > - Something else? > > > There is k8s bits that did not exist in the past now. The cloud auto > provisioning of agents, some community helm charts (and I think a k8s > operator, but I have never used it as CloudBees has a different > implementation). > There is soon (thanks to a PR) shotly going to be k8s secret support for > both global and secret credentials (so mix C-asC and K8s in one)... (I > should possibly do a blog post on that!) > > /James > > On Tue, 26 Jan 2021 at 11:26, Oleg Nenashev <o.v.nenas...@gmail.com> > wrote: > >> Marketing releases are indeed something we could consider. The next LTS >> baseline selection starts this week, with ETA in early April. This release >> will include a number of serious changes, and generally 3.0 might be >> justified from the technical point of view. At the same time, it IMHO >> requires a more fundamental change in Jenkins itself and its usage >> paradigm. For example, in Jenkins 2 we were mostly promoting Jenkins >> Pipeline and a few other related features, not the plugin unbundling as a >> breaking change. If the whole point is about marketing, we need to prepare >> well and to coordinate the rollout with CDF and key vendors so that we have >> a big marketing push. >> >> We do not have a fresh new massive story to share. At the same time there >> could be a few changes to highlight: >> >> - Adoption of Configuration-as-Code as a recommended way to manage >> Jenkins. >> - Making emphasis on Jenkins-in-the-cloud applications and packaging, >> with making Docker/Helm/etc. and downstream projects being promoted as >> first class citizens >> - Something else? >> >> Anyway, I am not sure about taking the next LTS as 3.0. Tables to divs >> story is likely to be a problem for users due to regressions in various >> in-house and not popular plugins which have not been fixed yet. Thanks to >> Tim, Raihaan, Felix and many other contributors for the cleanup, but I >> doubt it will be as smooth as Jenkins 1->2 upgrade for the users. >> >> Best regards, >> Oleg >> >> P.S: If we do a major release, it would be awesome to get the terminology >> cleanup finished at least for the Jenkins core and major plugins. Taking >> our announcements this summer, this is not the topic we should roll over to >> Jenkins 3. >> >> >> On Monday, January 25, 2021 at 6:53:59 PM UTC+1 msi...@cloudbees.com >> wrote: >> >>> That's a good point. I still see people who don't know about pipelines >>> even though they've been around since Jenkins 2.0 IIRC. The updated UI >>> is also less well known. >>> >>> On Fri, Jan 22, 2021 at 9:23 PM Ming Tang <gstan...@gmail.com> wrote: >>> > >>> > 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 jenkinsci-de...@googlegroups.com. >>> > To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/9d0ad61c-e63e-47d5-9034-1b648e002198n%40googlegroups.com. >>> >>> >>> >>> >>> -- >>> Matt Sicker >>> Senior Software Engineer, CloudBees >>> >> -- >> 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 jenkinsci-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/4d5673c0-a69d-489e-a7fe-5a8545ddfccen%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/4d5673c0-a69d-489e-a7fe-5a8545ddfccen%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAPzq3pf%3D7Vtp2GUUrD2vLrv8XoMXCxoPGQd-pSsoF_GzJDZUvw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPzq3pf%3D7Vtp2GUUrD2vLrv8XoMXCxoPGQd-pSsoF_GzJDZUvw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifVqhMzjOSa_Dg-Wf7o1JheVnHn5v4jD1ry-AtMVzV%3DLA%40mail.gmail.com.
