Calligra/Schedules: Difference between revisions
< Calligra
| Line 8: | Line 8: | ||
* [[/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>. | * [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''. | ||
Revision as of 22:08, 3 March 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.
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.
| Version | Features | Releases | 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 |