Calligra/Schedules/2.5/Release Plan: Difference between revisions
Appearance
No edit summary |
|||
Line 22: | Line 22: | ||
= Stable releases = | = Stable releases = | ||
== 2.5.0 == | |||
* Tagging August 3rd (no big merge on that day) | |||
* Release August 8th | |||
== 2.5.1 == | |||
* Tagging September 7th (no big merge on that day) | |||
* Release September 12th | |||
== 2.5.2 == | |||
* Tagging October 5th (no big merge on that day) | |||
* Release October 10th | |||
== 2.5.3 == | |||
* Tagging November 2th (no big merge on that day) | |||
* Release November 7th | |||
The final release should happen within three weeks after the RC. | The final release should happen within three weeks after the RC. |
Revision as of 08:05, 7 August 2012
See also: Feature Plan, Quality Control
Freezes
Master is never frozen for features or strings. The branch calligra/2.5 is always frozen for features or strings.
Testing
Alpha (2.4.90)
- Tagging May 25th (no big merge on that day)
- Release May 30th
Beta (2.4.91)
- Tagging and branching (calligra/2.5) June 15th (no big merge on that day)
- Release June 20th
RC (2.4.92)
- Tagging July 13th (no big merge on that day)
- Release July 18th
Stable releases
2.5.0
- Tagging August 3rd (no big merge on that day)
- Release August 8th
2.5.1
- Tagging September 7th (no big merge on that day)
- Release September 12th
2.5.2
- Tagging October 5th (no big merge on that day)
- Release October 10th
2.5.3
- Tagging November 2th (no big merge on that day)
- Release November 7th
The final release should happen within three weeks after the RC.