did you think of potential security issues and the need to to backport to the 4.x line so that older (commercially supported) LTS lines can upgrade?
> Are there pitfalls or problems that I have not considered in making the Jenkins version required by git plugin 5.0 be Jenkins 2.190.3?
did you think of potential security issues and the need to to backport to the 4.x line so that older (commercially supported) LTS lines can upgrade?
--
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/e3a200be-8901-4071-8398-fb6baea987e4%40googlegroups.com.
> On 26. Mar 2020, at 14:43, Mark Waite wrote:
>
> Are there pitfalls or problems that I have not considered in making the Jenkins version required by git plugin 5.0 be Jenkins 2.190.3?
2.190.x requires the BOM (-Duse-jenkins-bom) otherwise it won't compile out of the box. At least that's how I solved it for matrix-auth.
2.190.x seems like a solid choice at the moment, and also won't have implied dependencies as of today. But if the beta cycle is as long as it was for the previous major line, I'd recommend going with a more recent baseline; 2.138.x was a bad choice by the time Git Plugin 4.0.0 was finally released: obsolete for almost a year, two implied dependencies on newest releases, and its update center was retired just a month later.
--
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/3282626D-CB14-4C9E-BBAC-1C3F3E440A20%40beckweb.net.
I think 2.204.x is the current favorite, but I don't think there is anything against 2.190 more than age.
--
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/dff7cc14-6220-4e1d-bc4d-0cb8de893c98%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkin...@googlegroups.com.
--
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/CANfRfr035Sn9SKtVj9OE0JYvSYOx1oQE%3D9bg%3D6RxJYjem6N2wg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFjJ_HSWJxkvYJZ0Li8wWHUseFDczpBDd43wovjbQZ25w%40mail.gmail.com.
On Thu, Mar 26, 2020 at 5:29 PM Mark Waite <mark.ea...@gmail.com> wrote:
> confusion caused when users mistakenly decide to use git plugin 3.x with git client plugin 3.x.
Are there incompatible changes in `git-client` that would mean you
cannot use an older `git`?
> Is it a general practice that we can change the minimum Jenkins version without updating the major number?
No.
--
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/CANfRfr3jGyBTMYj%2BXaQ8TuPkJvOE7zku%3D%3Df8u%2BV0%3DwzJWKdUdw%40mail.gmail.com.