Calligra/Schedules/2.6/Release Plan: Difference between revisions
No edit summary |
No edit summary |
||
| Line 20: | Line 20: | ||
* Tagging November 24th (no big merge on that day) | * Tagging November 24th (no big merge on that day) | ||
* Release November 28th | * Release November 28th | ||
== RC2 (2.5.93) == | |||
Was sometime in december | |||
== RC3 (2.5.94) == | |||
* Tagging 12th December | |||
* Release 15th December | |||
= Stable releases = | = Stable releases = | ||
== 2.6.0 == | |||
* Tagging 2nd February | |||
* Release 5th February | |||
The first stable release should happen about three weeks after the RC, if everything is in order. | The first stable release should happen about three weeks after the RC, if everything is in order. | ||
Revision as of 10:25, 23 January 2013
See also: Feature Plan, Quality Control
Note
Status: in development, Alpha
Freezes
Master is never frozen for features or strings. The branch calligra/2.6 is always frozen for features or strings.
Testing
Alpha (2.5.90)
- Tagging October 5th (no big merge on that day)
- Release October 10th
Beta (2.5.91)
- Tagging and branching (calligra/2.6) October 26th (no big merge on that day)
- Release October 31th
RC (2.5.92)
- Tagging November 24th (no big merge on that day)
- Release November 28th
RC2 (2.5.93)
Was sometime in december
RC3 (2.5.94)
- Tagging 12th December
- Release 15th December
Stable releases
2.6.0
- Tagging 2nd February
- Release 5th February
The first stable release should happen about three weeks after the RC, if everything is in order.