> While I understand the reasoning for using the latest patch version of an LTS I think this increases the number of unneeded version upgrades for plugin authors.
warning: unpopular optinion follows as does accepting *any* update to the BOM in your plugin when you do not need a new API provided by a plugin that has been updaded/added in the bom. Testing (binary api) of the compatibility set is done in the BOM itself, so you should already know your code tests correctly (at a binary level, maybe not source code) so this is mostly in my experience busy work for no gain. On Monday, January 31, 2022 at 3:11:55 PM UTC [email protected] wrote: > The docs are here: > https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/ > > While I understand the reasoning for using the latest patch version of an > LTS I think this increases the number of unneeded version upgrades for > plugin authors. Due to this unnecessary version change in configuration as > code the git plugin needs to increase the version. When Mark releases this > change in the git plugin as well, I need to change my git-forensics plugin > as well, … and so on. The number of plugin upgrades increases just because > the LTS patch version increases, this is just a lot of additional work for > nothing. > > Am 31.01.2022 um 16:02 schrieb 'Jesse Glick' via Jenkins Developers < > [email protected]>: > > I am not sure there is a consensus yet in this area; see discussion in > https://github.com/jenkinsci/archetypes/pull/376#discussion_r781199364 > and elsewhere. My inclination is to require 2.289.3; there does not seem to > be much point in testing against an outdated LTS point release, especially > one that predates a security advisory and which no one should be running in > production. I will file a docs PR making that policy change and see where > the discussion goes. > > -- > 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/CANfRfr3xQW9u%2B-7jBjvqoiqO%2B283ZNJ0HYvkweR2-Gh_%2By1bjA%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3xQW9u%2B-7jBjvqoiqO%2B283ZNJ0HYvkweR2-Gh_%2By1bjA%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bb0586df-8b64-4575-a4e2-3c4fe38e9c21n%40googlegroups.com.
