Calligra/Schedules: Difference between revisions
< Calligra
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{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|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. | {{Note|All information and plans must be taken with caution and are subject to change. Decisions are taken on the [email protected] mailing list.}} | ||
* [[/Freezes|The meaning of freezes]] | * [[/Freezes|The meaning of freezes]] | ||
* [[/Release_Blockers|All about the release blockers]] | * [[/Release_Blockers|All about the release blockers]] | ||
* [[/How to write meaningful commit messages for the changelog/]] | * [[/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, rc, stable). To display tags, type <tt>git show-ref --tags</tt> or in gitk use ''File→List references''. | * [http://book.git-scm.com/3_git_tag.html Git tags] are used to mark releases in the code (alpha, beta, rc, stable). To display tags, type <tt>git show-ref --tags</tt> or in gitk use ''File→List references''. | ||
*See also: [[Calligra/Release_Howto|Release Howto]]. | |||
Revision as of 09:40, 9 July 2014
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, rc, stable). To display tags, type git show-ref --tags or in gitk use File→List references.
- See also: Release Howto.
Stages: Planned Development (pre-alpha, beta) Development (RC) Stable
| Version | Features | Releases | Quality Control |
|---|---|---|---|
| Calligra 3.0 | Feature Plan | Release Plan | Quality Control |
| Calligra 2.9 | Feature Plan | Release Plan | Quality Control |
| Calligra 2.8 | 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 |