On Thu, Mar 26, 2020 at 8:37 AM Robert Sandell <[email protected]> wrote:
> I think 2.204.x is the current favorite, but I don't think there is > anything against 2.190 more than age. > > Thanks for that insight. I hadn't reviewed the deployment statistics when I sent my proposal for 2.190.x. Based on deployment statistics, it seems like 2.204 or 2.204.1 are a better choice than 2.190.3. Stats show: - Almost 10x more installations of git client plugin on Jenkins 2.204.2 than any other single release (over 40 000 installations) - 53% of git client plugin installations are running 3.0.0 or newer - Almost 10x more installations of git plugin on Jenkins 2.204.2 than any other single release (over 40 000 installations) - 48% of git plugin installations are running 4.0.0 or newer I interpret that to mean that half the users are "staying current" with at least Jenkins 2.204. That half of users are also the most likely to update to git plugin 5.0 and git client plugin 5.0. I think the proposal should be revised to base on Jenkins 2.204.1 with a 1-2 month beta period (instead of 18 months). Are there significant negatives to choosing 2.204.1 instead of 2.190.3? Mark Waite > /B > > On Thursday, March 26, 2020 at 2:43:45 PM UTC+1, Mark Waite wrote: >> >> The git plugin and git client plugin currently require Jenkins 2.138.4. >> I chose that Jenkins version almost 18 months ago while working on the >> transition from JGit 4 to JGIt 5. >> >> I think it is time to switch the minimum Jenkins version for the git >> plugin and the git client plugin. I propose that the minimum Jenkins >> version for git plugin 5.0 and git client plugin 5.0 will be Jenkins >> 2.190.3. >> >> We can still release versions of the git plugin and git client plugin for >> Jenkins releases older than 2.190.3 by basing those releases on earlier >> branches. >> >> I frequently test the git plugin and git client plugin with the current >> Jenkins LTS line. I sometimes test with the prior Jenkins LTS line. >> Choosing 2.190.3 seems conservative enough to me and is much closer to what >> I'm actually testing than Jenkins 2.138.4. >> >> 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? >> >> Fran and Bobby, what do you think of the idea? >> >> Thanks, >> Mark Waite >> > -- > 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/dff7cc14-6220-4e1d-bc4d-0cb8de893c98%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/dff7cc14-6220-4e1d-bc4d-0cb8de893c98%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGWk7-fjL16fDkTBGjCXhQgD79uB_Qft1oggAC6TMm4_w%40mail.gmail.com.
