Calligra/Schedules
Appearance
< Calligra
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.5 | Feature Plan | 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 |
Release Checklist
- Collect changelog items
- Collect screenshots
- Major release: Create tour
- Update version on http://userbase.kde.org/Calligra/Download
- Update info on http://userbase.kde.org/Calligra/Download
- Update stable release version at [http://community.kde.org
/index.php?title=Template:Calligra/Stable&action=edit community.kde.org]
- Major release: Update stable major version at community.kde.org
- Major release: Update unstable major version at community.kde.org
- Write announcement for calligra.org
- Kexi
- Update kexi-project.org
- Add link to the Calligra announcement
- Update Kexi version on the front page
- Optional: Publish news on http://forum.kde.org/viewforum.php?f=220
- Publish news on http://identi.ca/kexi
- Major release: Publish news on http://www.linkedin.com
- Update kexi-project.org
- Wikipedia
- Update version