Calligra/Release Howto
< Calligra
This page contains notes on what needs to be done when releasing a new version of Calligra.
Tarball creation
- Create tarball using release-calligra.rb (from calligra's release scripts )
- Upload http://download.kde.org/stable/calligra-X.Y.Z/calligra-X.Y.Z.tar.xz, calligra-l10n/ and MD5SUMS*
- Remove previous files http://download.kde.org/stable/calligra-latest/calligra-*.tar.xz
- Upload http://download.kde.org/stable/calligra-latest/calligra-X.Y.Z.tar.xz, calligra-l10n/ and MD5SUMS*
Branching
Code
git checkout -b calligra/${VERSION} git push origin calligra/${VERSION}
(VERSION = 2.4, 2.5, etc.)
Translation
As a general advice it's better to move messages when scripty is not running, so before 1 AM CE(S)T (or UTC, I don't remember now) or after ~8:30 AM (same timezone as starting time).
Prepare yourself for a lot of suffering:
- warn the i18n coordinator in advance
- copy translation to stable-kde4 (use the calligra-release.rb scripts in calligra's release scripts )
- update scripty for stable translations (edit scripts/get_paths change the get_path function, and check that list_modules contains calligra):
svn co svn+ssh://[email protected]/home/kde/branches/stable/l10n-kde4/scripts scripts-stable
- update scripty for trunk translations
svn co svn+ssh://[email protected]/home/kde/trunk/l10n-kde4/scripts scripts-trunk
- update branches/stable/l10n-kde4/scripts/documentation_paths with the calligra git branch
- announce it to translators (CCMAIL:[email protected])
- update branch in calligra project page settings: https://projects.kde.org/projects/calligra/settings
Information updates
Maintainer of this section: Jstaniek (talk)
- Update version info in the source code:
- bump version info to N for libs in calligra/CMakeLists.txt (10 for 2.5, 11 for 2.6...)
set(GENERIC_CALLIGRA_LIB_VERSION "N.0.0")
set(GENERIC_CALLIGRA_LIB_SOVERSION "N") - update version info in calligra/libs/main/calligraversion.h:
#define CALLIGRA_VERSION_STRING "x.y Alpha|Beta|RC"
#define CALLIGRA_VERSION_MAJOR x
#define CALLIGRA_STABLE_VERSION_MINOR y
#define CALLIGRA_VERSION_RELEASE 89 (Alpha)|91 (Beta)|92 (RC)
#define CALLIGRA_ALPHA 0|1|2|...
#define CALLIGRA_BETA 0|1|2|...
#define CALLIGRA_RC 0|1|2|...
#define CALLIGRA_STABLE 0|1
- bump version info to N for libs in calligra/CMakeLists.txt (10 for 2.5, 11 for 2.6...)
- Collect changelog items
- Collect screenshots
- Write announcement for calligra.org
- Ask for proofreading at [email protected]
- See which packages will be ready at release day (*Linux, Windows, OSX), push people to have them ready
- Set version tag in git repo to the commit the tarball is made from
- Add version for all Calligra bug.kde.org products
- Major release:
- Create tour
- Update stable major version at community.kde.org and userbase.kde.org
- Update unstable major version at community.kde.org and userbase.kde.org
- Update color at http://community.kde.org/Calligra/Schedules#Important_information
- Update info on http://userbase.kde.org/Calligra/Download
- Update stable release version at community.kde.org and userbase.kde.org
- Update info in channel topic of #calligra and #kexi
- Update unstable stage at community.kde.org and userbase.kde.org
- Ask admin to update build.kde.org config to point to right major version for stable: config/projects/calligra.cfg (when master/stable != translation devel/stable) and http://quickgit.kde.org/?p=repo-management.git&a=blob&f=hooks%2Fpost-update
- Email [email protected] [email protected]
- Publish news on Calligra Facebook page
- Publish news on Calligra forum: https://forum.kde.org/viewforum.php?f=203
- Wikipedia
- Update version at http://en.wikipedia.org/wiki/Calligra and http://pl.wikipedia.org/wiki/Calligra
- Kexi: moved to Kexi/Releases/Howto