diff --git a/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc b/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc
index 2f19e0cb88ec..35836dc32378 100644
--- a/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc
+++ b/content/doc/developer/plugin-development/choosing-jenkins-baseline.adoc
@@ -14,7 +14,7 @@ In particular, the LTS Release Line is based on slightly older releases to provi
 * *Building against recent Jenkins versions* allows you to use recently added core features and API from your plugin. 
 You will also use that newer version for `mvn hpi:run`, so it may be easier to test your plugin with newer Jenkins releases. 
 Additionally, since features are sometimes moved from core into plugins, depending on a more recent Jenkins version will make your plugin's dependencies on what used to be core features explicit, otherwise your plugin will not work.
-* *Use at least the minimum version supported by the update center*, the supported update center versions can be found at link:https://updates.jenkins.io[updates.jenkins.io], at the time of writing (2020-03) this is 2.164.x.
+* *Use at least the minimum version supported by the update center*, the supported update center versions can be found at link:https://updates.jenkins.io/tiers.json[updates.jenkins.io/tiers.json], at the time of writing (2020-09-02) this is 2.176.2.
 
 There are link:https://stats.jenkins.io/pluginversions/[statistics of core versions by plugin] that can help you decide.