From ddf2df2f320fc0a4f1a71091de1b54779b0ad7bb Mon Sep 17 00:00:00 2001 From: Justin Mclean Date: Mon, 26 Oct 2026 07:12:36 +1100 Subject: [PATCH 1/2] Document where markdownlint rules are listed Add a note to .markdownlint-cli2.yaml pointing to the markdownlint rules list and explaining how to turn a rule off. --- .markdownlint-cli2.yaml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.markdownlint-cli2.yaml b/.markdownlint-cli2.yaml index c8cb51a6f..b3a4adfb5 100644 --- a/.markdownlint-cli2.yaml +++ b/.markdownlint-cli2.yaml @@ -1,4 +1,7 @@ -# A list explaining what each rule does is available at https://rumdl.dev/rules/ +# Config for markdownlint-cli2, run by the pre-commit hook in +# .pre-commit-config.yaml. Rule IDs (MD001 and so on) are listed at +# https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md +# To turn a rule off, add "MDxxx: false" under config: below. # Pelican metadata (Title:, license: and so on) is not Markdown. frontMatter: "^(?:[A-Za-z][\\w-]*:.*\\r?\\n)+" From aa437cf3d2cf36ade5426d02c2e7a5398bfc6d18 Mon Sep 17 00:00:00 2001 From: Justin Mclean Date: Mon, 26 Oct 2026 09:48:09 +1100 Subject: [PATCH 2/2] Fix markdownlint MD022 in app-upgrade-policy.md Add a blank line below each subheading so the page passes the blanks-around-headings rule that CI enforces. --- content/pages/app-upgrade-policy.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/pages/app-upgrade-policy.md b/content/pages/app-upgrade-policy.md index b5b01381c..c87f9c502 100644 --- a/content/pages/app-upgrade-policy.md +++ b/content/pages/app-upgrade-policy.md @@ -6,11 +6,13 @@ This policy encompasses Infra's approach to upgrades of Jenkins, Confluence and ## Jenkins ### Main Jenkins instance + _Upgrades once a quarter_ Infra follows the LTS line of releases, which the Jenkins Project releases on a 12-week cycle. Once every three months, on the last Saturday or Sunday of the month following the Jenkins LTS release, ASF Infra upgrades the main instance. ### Jenkins plugins + _Upgrade once a month_ We upgrade all plugins (there are more than 200!) before and after the main instance upgrade, as appropriate, and at the end of each month when there is no main instance upgrade to perform. @@ -18,11 +20,13 @@ We upgrade all plugins (there are more than 200!) before and after the main inst ## Jira ### Main Jira instance + _Upgrades every six months_ Jira gets a new release every two to six weeks, far too often (and unpredictable) for us to upgrade every release they make. Infra upgrades our Jira instance to whatever the latest release is every six months. ### Jira plugins + _Upgrade every two months_ We upgrade Jira plugins before or after each main instance upgrade, as appropriate, and once every two months between main instance upgrades. @@ -30,11 +34,13 @@ We upgrade Jira plugins before or after each main instance upgrade, as appropria ## Confluence ### Main Confluence instance + _Upgrades every six months_ Our goal is to upgrade Confluence to the latest version twice a year. ### Confluence plugins + _Upgrade every two months_ Every two months we perform upgrades to plugins that are compatible with the version of the main Confluence instance we are running.