Calligra/Schedules: Difference between revisions

Latest revision as of 11:41, 11 October 2015

Note

During the development of Calligra, the team sets feature goals, and schedule for upcoming releases. This helps to know when to concentrate on features, bug fixing, cleaning, brainstorming, this also allow for an external person to know what to expect and when.

Note

All information and plans must be taken with caution and are subject to change. Decisions are taken on the [email protected] mailing list.

The meaning of freezes
All about the release blockers
How to write meaningful commit messages for the changelog
Git tags are used to mark releases in the code (alpha, beta, stable). To display tags, type git show-ref --tags or in gitk use File→List references.
See also: Release Howto.

Stages: Planned Development (alpha, beta) Stable

Version	Features	Releases	Quality Control
Calligra 3.1	Feature Plan	Release Plan
Calligra 3.0	Feature Plan	Release Plan
Calligra 2.9	Feature Plan	Release Plan
Calligra 2.8	Feature Plan	Release Plan
Calligra 2.7	Feature Plan	Release Plan
Calligra 2.6	Feature Plan	Release Plan
Calligra 2.5	Feature Plan (see also old page)	Release Plan
Calligra 2.4	Feature Plan	Release Plan	Quality Control
KOffice 2.3	Feature Plan	Release Plan	Quality Control
KOffice 2.2	Feature Plan	Release Plan
KOffice 2.1	Feature Plan	Release Plan
KOffice 2.0	Feature Plan	Release Plan	Applications Status

@@ Line 1: / Line 1: @@
-During the development of KOffice, the team sets goals in features, and dates for upcoming releases. This help to know when to concentrate on features, bug fixing, cleaning, brainstorming, this also allow for an external person to know what to expect and when.
+{{Note|During the development of Calligra, the team sets '''feature goals, and schedule for upcoming releases'''. This helps to know when to concentrate on features, bug fixing, cleaning, brainstorming, this also allow for an external person to know what to expect and when.}}
+{{Note|All information and plans must be taken with caution and are subject to change. Decisions are taken on the [email protected] mailing list.}}
-All information and plans must be taken with caution and are subject to changes without notices, decisions are taken on the [email protected] mailing list.
-== Important information ==
 * [[/Freezes|The meaning of freezes]]
 * [[/Release_Blockers|All about the release blockers]]
 * [[/How to write meaningful commit messages for the changelog/]]
+* [http://book.git-scm.com/3_git_tag.html Git tags] are used to mark releases in the code (alpha, beta, stable). To display tags, type <tt>git show-ref --tags</tt> or in gitk use ''File&rarr;List references''.
+*See also: [[Calligra/Release_Howto|Release Howto]].
+<small style="color:black;">Stages: <span style="border: 1px solid black;padding:0.2em;">Planned</span> <span style="background-color:#FFCC99;border: 1px solid black;padding:0.2em;">Development (alpha, beta)</span> <span style="background-color:{{LightGreen}};border: 1px solid black;padding:0.2em;">Stable</span></small>
 {{TableStart}}
@@ Line 16: / Line 17: @@
 !Quality Control
 |-
+|Calligra 3.1
+|[[/Feature Plan/]]
+|[[/3.1/Release_Plan|Release Plan]]
+|
+|- valign=top style="background-color:#FFCC99;"
+|Calligra 3.0
+|[[/Feature Plan/]]
+|[[/3.0/Release_Plan|Release Plan]]
+|
+{{GreenRow}}
+|Calligra 2.9
+|[[/Feature Plan/]]
+|[[/2.9/Release_Plan|Release Plan]]
+|
+{{GreenRow}}
+|Calligra 2.8
+|[[/Feature Plan/]]
+|[[/2.8/Release_Plan|Release Plan]]
+|
+{{GreenRow}}
+|Calligra 2.7
+|[[/Feature Plan/]]
+|[[/2.7/Release_Plan|Release Plan]]
+|
+{{GreenRow}}
+|Calligra 2.6
+|[[/Feature Plan/]]
+|[[/2.6/Release_Plan|Release Plan]]
+|
+{{GreenRow}}
+|Calligra 2.5
+|[[/Feature Plan/]] ([[/2.5/Feature_Plan|see also old page]])
+|[[/2.5/Release_Plan|Release Plan]]
+|
+{{GreenRow}}
 |Calligra 2.4
 |[[/2.4/Feature_Plan|Feature Plan]]