Skip to content

Document where markdownlint rules are listed #325

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cottage14 merged 2 commits into from
Oct 26, 2026
Merged

Document where markdownlint rules are listed #325

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ddf2df2
Document where markdownlint rules are listed
justinmclean Oct 25, 2026
aa437cf
Fix markdownlint MD022 in app-upgrade-policy.md
justinmclean Oct 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion .markdownlint-cli2.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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)+"
Expand Down
6 changes: 6 additions & 0 deletions content/pages/app-upgrade-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,35 +6,41 @@ This policy encompasses Infra's approach to upgrades of Jenkins, Confluence and
## Jenkins

### Main Jenkins instance

_Upgrades once a quarter_

Infra follows the <a href="https://jenkins.io/download/lts/" target="_blank">LTS line of releases</a>, 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.

## 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.

## 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.
Expand Down
Loading