Calligra/Release Howto: Difference between revisions

From KDE Community Wiki
Line 47: Line 47:
** Update version on [http://kde-apps.org/content/show.php?content=12365 KDE-Apps.org]
** Update version on [http://kde-apps.org/content/show.php?content=12365 KDE-Apps.org]
** Optional: Publish news on http://forum.kde.org/viewforum.php?f=220
** Optional: Publish news on http://forum.kde.org/viewforum.php?f=220
** Publish news on http://identi.ca/kexi
** Publish news on http://identi.ca/kexi and https://twitter.com/kexi_project
** Publish news on [email protected]
** Publish news on [email protected]
** Major release: Publish news on http://www.linkedin.com
** Major release: Publish news on http://www.linkedin.com
* Wikipedia
* Wikipedia
** Update version at http://en.wikipedia.org/wiki/Calligra and http://pl.wikipedia.org/wiki/Calligra
** Update version at http://en.wikipedia.org/wiki/Calligra and http://pl.wikipedia.org/wiki/Calligra

Revision as of 20:45, 27 January 2013

This page contains notes on what needs to be done when releasing a new version of Calligra.

Note

This is work in progress. You can contribute to this page or request updates.


Tarball creation

Branching

Code

git checkout -b calligra/${VERSION}
git push origin calligra/${VERSION}

Translation

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+ssh://[email protected]/home/kde/branches/stable/l10n-kde4/scripts

Information updates