Skip to content

Commit 61049f4

Browse files
authored
Update app-upgrade-policy.md fixed errors in section title formatting
1 parent aee2ae9 commit 61049f4

1 file changed

Lines changed: 16 additions & 18 deletions

File tree

‎content/pages/app-upgrade-policy.md‎

Lines changed: 16 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -3,45 +3,43 @@ license: https://www.apache.org/licenses/LICENSE-2.0
33

44
This policy encompasses Infra's approach to upgrades of Jenkins, Confluence and Jira and their respective plugins.
55

6-
# Upgrades
6+
## Jenkins
77

8-
### Jenkins
9-
10-
**Main Jenkins instance**
8+
### Main Jenkins instance
119
_Upgrades once a quarter_
1210

13-
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.
11+
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.
1412

15-
**Jenkins plugins**
16-
_Upgrades once a month_
13+
### Jenkins plugins
14+
_Upgrade once a month_
1715

1816
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.
1917

20-
### Jira
18+
## Jira
2119

22-
**Main Jira instance**
20+
### Main Jira instance
2321
_Upgrades every six months_
2422

2523
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.
2624

27-
**Jira plugins**
28-
_Upgrades every two months_
25+
### Jira plugins
26+
_Upgrade every two months_
2927

3028
We upgrade Jira plugins before or after each main instance upgrade, as appropriate, and once every two months between main instance upgrades.
3129

32-
### Confluence
30+
## Confluence
3331

34-
**Main Confluence instance**
32+
### Main Confluence instance
3533
_Upgrades every six months_
3634

3735
Our goal is to upgrade Confluence to the latest version twice a year.
3836

39-
**Confluence plugins**
40-
_Upgrades every two months_
37+
### Confluence plugins
38+
_Upgrade every two months_
4139

4240
Every two months we perform upgrades to plugins that are compatible with the version of the main Confluence instance we are running.
4341

44-
# Documentation
42+
## Documentation
4543

4644
Infra documents what we upgraded and when, from what version to what version, on these pages:
4745

@@ -52,10 +50,10 @@ Infra documents what we upgraded and when, from what version to what version, on
5250
- <a href="https://cwiki.apache.org/confluence/display/INFRA/Confluence+Upgrades" target="_blank">Confluence upgrades</a>
5351
- <a href="https://cwiki.apache.org/confluence/display/INFRA/Confluence+Plugin+Upgrades" target="_blank">Confluence plugin upgrades</a>
5452

55-
# Notifications
53+
## Notifications
5654

5755
Since Jenkins, Jira and Confluence are **Core Services**, Infra issues a notice of a planned upgrade at least 72 hours ahead of the event on the wiki or a web page and by emails to the `[email protected]`, `[email protected]` and `[email protected]` mailing lists.
5856

59-
# In case of emergencies
57+
## In case of emergencies
6058

6159
Occasionally things go wrong with a main or plugin upgrade, and security issues may arise. If we determine that there is an issue, we will work on it immediately until we resolve it. We will send an email to the relevant list about any unexpected downtime.

0 commit comments

Comments
 (0)