From 331c091e4717047a4a6bf5fe6343932b5f7a1f0f Mon Sep 17 00:00:00 2001 From: James Nord Date: Mon, 13 Jun 2022 12:01:35 +0100 Subject: [PATCH 1/2] ignore recomendations for API plugins following these recommendations for API plugins would be wrong. The reasons provided in the original PRs for doing so are all completely moot with an API plugin, and would lock out of any older version getting API fixes - esp security related ones or at least make it much more effort than would be required to deliver it. --- .../plugin-development/choosing-jenkins-baseline.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc b/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc index bf761ba95654..2beecf3ef9b0 100644 --- a/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc +++ b/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc @@ -32,6 +32,9 @@ There are link:https://stats.jenkins.io/pluginversions/[statistics of core versi These are updated monthly. When updating the core dependency, choose the link:/changelog-stable/[newest LTS version] that doesn't exclude a majority of your existing users (by requiring a newer Jenkins than they have). +NOTE: if you are packaging a pure API library (one that does not depend on Jenkins APIs) then you should ignore newer jenkins versions and pick an older LTS. +Something around 1 year old that does not have too many detached plugins makes a good choice and *PLACEHOLDER_OLDEST_LTS* would be a reasonable candidate. + ## Currently recommended versions At the moment, the Jenkins releases *PLACEHOLDER_RECENT_LTS_POINT_HIGHS* make good core dependencies. From ed82e96336f6a39901aacba7841250be5f645020 Mon Sep 17 00:00:00 2001 From: Mark Waite Date: Mon, 13 Jun 2022 16:46:30 -0600 Subject: [PATCH 2/2] Fix capitalization Co-authored-by: Jesse Glick --- .../developer/plugin-development/choosing-jenkins-baseline.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc b/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc index 2beecf3ef9b0..9471a4ba4368 100644 --- a/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc +++ b/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc @@ -32,7 +32,7 @@ There are link:https://stats.jenkins.io/pluginversions/[statistics of core versi These are updated monthly. When updating the core dependency, choose the link:/changelog-stable/[newest LTS version] that doesn't exclude a majority of your existing users (by requiring a newer Jenkins than they have). -NOTE: if you are packaging a pure API library (one that does not depend on Jenkins APIs) then you should ignore newer jenkins versions and pick an older LTS. +NOTE: If you are packaging a pure API library (one that does not depend on Jenkins APIs) then you should ignore newer Jenkins versions and pick an older LTS. Something around 1 year old that does not have too many detached plugins makes a good choice and *PLACEHOLDER_OLDEST_LTS* would be a reasonable candidate. ## Currently recommended versions