Difference between revisions of "Calligra/Release Howto"

Line 10: Line 10:
== Code ==
== Code ==
  svn mkdir https://svn.kde.org/home/kde/branches/koffice/${VERSION}
  git checkout -b calligra/${VERSION}
  svn cp https://svn.kde.org/home/kde/trunk/koffice https://svn.kde.org/home/kde/branches/koffice/${VERSION}
  git push origin calligra/${VERSION}
== Translation ==
== Translation ==

Revision as of 06:16, 3 March 2012

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

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

Tarball creation



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


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


  • 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

Content is available under Creative Commons License SA 4.0 unless otherwise noted.