Calligra/Schedules: Difference between revisions
< Calligra
| Line 35: | Line 35: | ||
|[[/2.6/Release_Plan|Release Plan]] | |[[/2.6/Release_Plan|Release Plan]] | ||
|[[/2.6/Release_Plan/Quality Control|Quality Control]] | |[[/2.6/Release_Plan/Quality Control|Quality Control]] | ||
{{ | {{GreenRow}} | ||
|Calligra 2.5 | |Calligra 2.5 | ||
|[[/Feature Plan/]] ([[/2.5/Feature_Plan|see also old page]]) | |[[/Feature Plan/]] ([[/2.5/Feature_Plan|see also old page]]) | ||
Revision as of 22:30, 16 September 2012
During the development of Calligra, 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.
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.
See also: Release Howto.
Important information
- 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, rc, stable). To display tags, type git show-ref --tags or in gitk use File→List references.
Stages: Planned Development (alpha, beta) Development (RC) Stable
| Version | Features | Releases | Quality Control |
|---|---|---|---|
| Calligra 3.0 | Feature Plan | Release Plan | Quality Control |
| Calligra 2.7 | Feature Plan | Release Plan | Quality Control |
| Calligra 2.6 | Feature Plan | Release Plan | Quality Control |
| Calligra 2.5 | Feature Plan (see also old page) | Release Plan | Quality Control |
| 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 |