Difference between revisions of "Calligra/Release Howto"

Jump to: navigation, search
(Information updates)
m (Translation)
Line 16: Line 16:
 
== Translation ==
 
== 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).
+
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:
 
Prepare yourself for a lot of suffering:

Revision as of 20:37, 1 December 2013

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

Note-box-icon.png
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}

(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

Information updates


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