Calligra/Release Howto: Difference between revisions
Appearance
< Calligra
Created page with 'This page contains notes on what needs to be done when releasing a new version of KOffice. __TOC__ = Tarball creation = = Branching = == Code == svn mkdir https://svn.kde.or...' |
No edit summary |
||
Line 1: | Line 1: | ||
This page contains notes on what needs to be done when releasing a new version of | This page contains notes on what needs to be done when releasing a new version of Calligra. | ||
{{InProgress}} | |||
__TOC__ | __TOC__ |
Revision as of 22:38, 18 December 2010
This page contains notes on what needs to be done when releasing a new version of Calligra.
Tarball creation
Branching
Code
svn mkdir https://svn.kde.org/home/kde/branches/koffice/${VERSION} svn cp https://svn.kde.org/home/kde/trunk/koffice https://svn.kde.org/home/kde/branches/koffice/${VERSION}
Translation
Prepare yourself for a lot of suffering:
- warn the i18n coordinator in advance
- copy translation to stable-kde4 (use the koffice-release.rb scripts in kde-common)
- update scripty for stable translations (edit scripts/get_paths change the get_path function, and check that list_modules contains koffice)
- check that stable-kde4/doocumentation has an external on the koffice's branch documentation
- announce it to translators (CCMAIL:[email protected])
Website update
Preparation:
- announcements/changelog-#{version}.php
- announcements/announce-#{version}.php
- releases/#{version}-release.php
- release notes translation:
* send the release notes a few days before release to kde-i18n-doc at kde.org * complete the page "announcements/announce-#{version}.php" with link to the translation that are usually hosted on KDE i18n local team websites
Last-minute changes:
- releases/index.php
- announcements/index.php
- site.inc
- news.rdf
- menu.inc