Calligra/Schedules/2.4/Release Plan: Difference between revisions
No edit summary |
No edit summary |
||
| (30 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
See also: [[../Feature Plan/]], [[../Quality Control/]] | See also: [[../Feature Plan/]], [[../Quality Control/]] | ||
{{Note|Status: | {{Note|Status: released}} | ||
For this release, we aim at making Calligra ready for users. We will start making a plan for beta and final releases once the feautres mark for user-readiness in the [[../Feature Plan/]] are implemented, for the time being, we will make monthly snapshots release for people interesting in watching the progress. | For this release, we aim at making Calligra ready for users. We will start making a plan for beta and final releases once the feautres mark for user-readiness in the [[../Feature Plan/]] are implemented, for the time being, we will make monthly snapshots release for people interesting in watching the progress. | ||
| Line 9: | Line 9: | ||
= Freezes = | = Freezes = | ||
== Soft Freeze, August 31th == | == Soft Freeze, August 31th, 2011 == | ||
No more features in master. Features in master are restricted to features discussed before hand and that can justify to be necesserary for user readiness. | No more features in master. Features in master are restricted to features discussed before hand and that can justify to be necesserary for user readiness. | ||
| Line 15: | Line 15: | ||
It is worthwhile to remember that while new features are allowed in the beta cycle, it should be the exception, not the norm. | It is worthwhile to remember that while new features are allowed in the beta cycle, it should be the exception, not the norm. | ||
== String Freeze, October 12th == | == String Freeze, October 12th, 2011 == | ||
Any changes to a string needs to be discussed with the translation teams (except for typo that are bug fix and you only need to ping the translation teams). It also means no new features can be added. | Any changes to a string needs to be discussed with the translation teams (except for typo that are bug fix and you only need to ping the translation teams). It also means no new features can be added. | ||
| Line 23: | Line 23: | ||
Unreleased. | Unreleased. | ||
== 2.3.71 == | == Alpha 1 (2.3.71) == | ||
* Tagging May 12th (no big merge on that day) | * Tagging May 12th (no big merge on that day) | ||
* Release May 18th | * Release May 18th | ||
== 2.3.72 == | == Alpha 2 (2.3.72) == | ||
* Tagging June 10th (no big merge on that day) | * Tagging June 10th (no big merge on that day) | ||
* Release June 16th | * Release June 16th | ||
== 2.3.73 == | == Alpha 3 (2.3.73) == | ||
* Tagging July 8th (no big merge on that day) | * Tagging July 8th (no big merge on that day) | ||
* Release July 13th | * Release July 13th | ||
== 2.3.74 == | == Alpha 4 (2.3.74) == | ||
* Tagging August 12th (no big merge on that day) | * Tagging August 12th (no big merge on that day) | ||
* Release August 17th | * Release August 17th | ||
| Line 47: | Line 47: | ||
== Beta 2 (2.3.82) == | == Beta 2 (2.3.82) == | ||
* Tagging September 30th (no big merge on that day) | * Tagging September 30th (no big merge on that day) | ||
** {{CalligraGitCommit|ea57cb68b4c7ea46c5916b2a54084159c8dce1ed}} | |||
* Release October 5th | * Release October 5th | ||
== Beta 3 (2.3.83) == | == Beta 3 (2.3.83) == | ||
* Tagging October 21th (no big merge on that day) | * Tagging October 21th (no big merge on that day) | ||
** {{CalligraGitCommit|49808577a77267dc7f4cd917588312e4aad59681}} | |||
* Release October 26th | * Release October 26th | ||
= | == Beta 4 (2.3.84) == | ||
* Tagging November 18th (no big merge on that day) | * Tagging November 18th (no big merge on that day) | ||
* Release November 23th | * Release November 23th | ||
== Beta 5 (2.3.85) == | |||
* Tagging December 9th (no big merge on that day) | |||
* Release December 14th | |||
== Beta 6 (2.3.86) == | |||
* Tagging January 6th (no big merge on that day) | |||
* Release January 11th | |||
== Beta 7 (2.3.87) == | |||
* Tagging January 27th (no big merge on that day) | |||
* Release February 1th | |||
= Release Candidate = | |||
There is no realistic way to be certain when the RC1 will be available, hopefully in 2012, we invite you to check [http://quality.calligra.org/] and when the number of tests failure and release critical bugs is near zero, then the time for the RC1 will be very close. | |||
== RC 1 (2.3.91) == | |||
* Tagging March 2nd (no big merge on that day), branching into the calligra/2.4 branch will happen at that time | |||
* Release March 7th | |||
= Final release and maintenance schedule = | |||
== 2.4.0 == | |||
Hopefully, it will happen three weeks after the RC, if no major problem is discovered. | |||
* Tagging April 6th (no big merge on that day) | |||
* Release April 11th | |||
== 2.4.1 == | |||
* Tagging April 21th (no big merge on that day) | |||
* Release April 25th | |||
== 2.4.2 == | |||
* Tagging May 25th (no big merge on that day) | |||
* Release May 30h | |||
== 2.4.3 == | |||
* Tagging June 26th (no big merge on that day) | |||
* Release June 27th | |||
== 2.4.4 == | |||
* Tagging January 19th (no big merge on that day) | |||
* Release January 22nd | |||
Latest revision as of 12:16, 15 January 2013
See also: Feature Plan, Quality Control
Note
Status: released
For this release, we aim at making Calligra ready for users. We will start making a plan for beta and final releases once the feautres mark for user-readiness in the Feature Plan are implemented, for the time being, we will make monthly snapshots release for people interesting in watching the progress.
Freezes
Soft Freeze, August 31th, 2011
No more features in master. Features in master are restricted to features discussed before hand and that can justify to be necesserary for user readiness.
It is worthwhile to remember that while new features are allowed in the beta cycle, it should be the exception, not the norm.
String Freeze, October 12th, 2011
Any changes to a string needs to be discussed with the translation teams (except for typo that are bug fix and you only need to ping the translation teams). It also means no new features can be added.
Snapshots
2.3.70
Unreleased.
Alpha 1 (2.3.71)
- Tagging May 12th (no big merge on that day)
- Release May 18th
Alpha 2 (2.3.72)
- Tagging June 10th (no big merge on that day)
- Release June 16th
Alpha 3 (2.3.73)
- Tagging July 8th (no big merge on that day)
- Release July 13th
Alpha 4 (2.3.74)
- Tagging August 12th (no big merge on that day)
- Release August 17th
Betas
Beta 1 (2.3.81)
- Tagging September 7th (no big merge on that day)
- Release September 14th
Beta 2 (2.3.82)
- Tagging September 30th (no big merge on that day)
- Release October 5th
Beta 3 (2.3.83)
- Tagging October 21th (no big merge on that day)
- Release October 26th
Beta 4 (2.3.84)
- Tagging November 18th (no big merge on that day)
- Release November 23th
Beta 5 (2.3.85)
- Tagging December 9th (no big merge on that day)
- Release December 14th
Beta 6 (2.3.86)
- Tagging January 6th (no big merge on that day)
- Release January 11th
Beta 7 (2.3.87)
- Tagging January 27th (no big merge on that day)
- Release February 1th
Release Candidate
There is no realistic way to be certain when the RC1 will be available, hopefully in 2012, we invite you to check [1] and when the number of tests failure and release critical bugs is near zero, then the time for the RC1 will be very close.
RC 1 (2.3.91)
- Tagging March 2nd (no big merge on that day), branching into the calligra/2.4 branch will happen at that time
- Release March 7th
Final release and maintenance schedule
2.4.0
Hopefully, it will happen three weeks after the RC, if no major problem is discovered.
- Tagging April 6th (no big merge on that day)
- Release April 11th
2.4.1
- Tagging April 21th (no big merge on that day)
- Release April 25th
2.4.2
- Tagging May 25th (no big merge on that day)
- Release May 30h
2.4.3
- Tagging June 26th (no big merge on that day)
- Release June 27th
2.4.4
- Tagging January 19th (no big merge on that day)
- Release January 22nd