mirror
/
wagtail
kopia lustrzana https://github.com/wagtail/wagtail
1
0
Forkuj 0
Kod Zgłoszenia Packages Projekty Wydania Wiki Aktywność

Updated Release schedule (markdown)

master
Thibaud Colas 2024-05-14 10:33:40 +01:00
rodzic 94203002a8
commit 54d4df90a3
1 zmienionych plików z 22 dodań i 10 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

32
Release-schedule.md

@ -1,14 +1,8 @@
New feature releases of Wagtail are released every three months. These releases provide new features, improvements and bugfixes, and are marked by incrementing the second part of the version number (for example, 2.6 to 2.7).
The actual release date will be on the closest working day (in the UK), and depend on the successful testing of release candidates, which are made available at least three weeks ahead of the planned final release date.
## Future and current versions
Additionally, patch releases will be issued as needed, to fix bugs and security issues. These are marked by incrementing the third part of the version number (for example, 2.6 to 2.6.1). Wherever possible, these releases will remain fully backwards compatible with the corresponding feature and not introduce any breaking changes.
A feature release will usually stop receiving patch release updates when the next feature release comes out. However, selected feature releases are designated as Long Term Support (LTS) releases, and will continue to receive maintenance updates to address any security and data-loss related issues that arise. Typically, a Long Term Support release will happen once every four feature releases and receive updates for five feature releases, giving a support period of fifteen months with a three month overlap.
Also, Long Term Support releases will ensure compatibility with at least one [Django Long Term Support release](https://www.djangoproject.com/download/#supported-versions).
Exceptionally, with 2.0 introducing breaking changes, 1.13 was designated as LTS in addition to 1.12.
Here are planned future releases and currently-supported Wagtail versions.
| Version | Release date | Active support | Security support |
| -------------- |-----------------------:| -------------------:| -------------------:|
@ -17,6 +11,16 @@ Exceptionally, with 2.0 introducing breaking changes, 1.13 was designated as LTS
| 6.1 | 1 May 2024 | 1 August 2024 | 1 November 2024 |
| 6.0 | 7 February 2024 | 1 May 2024 | 1 August 2024 |
| **5.2 LTS** | **1 November 2023** | **3 February 2025** | **3 February 2025** |
\* Future version numbers are provisional - these may receive a major version number increment, depending on the extent of backwards-incompatible changes and significant UI differences.
## Past versions
| Version | Release date | Active support | Security support |
| -------------- |-----------------------:| -------------------:| -------------------:|
| 6.1 | 1 May 2024 | 1 August 2024 | 1 November 2024 |
| 6.0 | 7 February 2024 | 1 May 2024 | 1 August 2024 |
| **5.2 LTS** | **1 November 2023** | **3 February 2025** | **3 February 2025** |
| 5.1 | 1 August 2023 | 1 November 2023 | 1 February 2024 |
| 5.0 | 2 May 2023 | 1 August 2023 | 1 November 2023 |
| 4.2 | 1 February 2023 | 2 May 2023 | 1 August 2023 |
@ -43,6 +47,14 @@ Exceptionally, with 2.0 introducing breaking changes, 1.13 was designated as LTS
| 1.4 LTS | March 2016 | December 2016 | December 2016 |
| 0.8 LTS | November 2014 | March 2016 | March 2016 |
## Provisional future versions
Exceptionally, with 2.0 introducing breaking changes, 1.13 was designated as LTS in addition to 1.12.
\* Future version numbers are provisional - these may receive a major version number increment, depending on the extent of backwards-incompatible changes and significant UI differences.
## How we schedule our releases
The actual release date will be on the closest working day (in the UK), and depend on the successful testing of release candidates, which are made available at least three weeks ahead of the planned final release date.
Additionally, patch releases will be issued as needed, to fix bugs and security issues. These are marked by incrementing the third part of the version number (for example, 2.6 to 2.6.1). Wherever possible, these releases will remain fully backwards compatible with the corresponding feature and not introduce any breaking changes.
A feature release will usually stop receiving patch release updates when the next feature release comes out. However, selected feature releases are designated as Long Term Support (LTS) releases, and will continue to receive maintenance updates to address any security and data-loss related issues that arise. Typically, a Long Term Support release will happen once every four feature releases and receive updates for five feature releases, giving a support period of fifteen months with a three month overlap.
Also, Long Term Support releases will ensure compatibility with at least one [Django Long Term Support release](https://www.djangoproject.com/download/#supported-versions).