Calligra/Release Howto: Difference between revisions

From KDE Community Wiki
(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
 
(58 intermediate revisions by 3 users not shown)
Line 1: Line 1:
This page contains notes on what needs to be done when releasing a new version of KOffice.
This page contains notes on what needs to be done when releasing a new version of Calligra.
 
{{InProgress}}


__TOC__
__TOC__


= Tarball creation =
= Tarball creation =
*Create tarball using release-calligra.rb (from [http://quickgit.kde.org/index.php?p=scratch%2Fberger%2Fcalligra-release-scripts.git&a=summary 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 =
= Branching =


== 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}
(VERSION = 2.4, 2.5, etc.)


== 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).
Prepare yourself for a lot of suffering:
Prepare yourself for a lot of suffering:
* warn the i18n coordinator in advance
* warn the i18n coordinator in advance
* copy translation to stable-kde4 (use the koffice-release.rb scripts in kde-common)
* copy translation to stable-kde4 (use the calligra-release.rb scripts in [http://quickgit.kde.org/index.php?p=scratch%2Fberger%2Fcalligra-release-scripts.git&a=summary calligra's release scripts ])
* update scripty for stable translations (edit scripts/get_paths  change the get_path function, and check that list_modules contains koffice)
* update scripty for stable translations (edit scripts/get_paths  change the get_path function, and check that list_modules contains calligra):
* check that stable-kde4/doocumentation has an external on the koffice's branch documentation
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])
* announce it to translators (CCMAIL:[email protected])
* update branch in calligra project page settings: https://projects.kde.org/projects/calligra/settings


= Website update =
= Information updates =
 
Maintainer of this section: [[User:Jstaniek|Jstaniek]] ([[User talk:Jstaniek|talk]])
Preparation:
*Update version info in the source code:
* announcements/changelog-#{version}.php
**bump version info to '''N''' for libs in calligra/CMakeLists.txt (10 for 2.5, 11 for 2.6...)<br/><tt>set(GENERIC_CALLIGRA_LIB_VERSION "'''N'''.0.0")<br/>set(GENERIC_CALLIGRA_LIB_SOVERSION "'''N'''")</tt>
* announcements/announce-#{version}.php
**update version info in calligra/libs/main/calligraversion.h:<br/><tt>#define CALLIGRA_VERSION_STRING "<b>x.y Alpha|Beta|RC</b>"<br/>#define CALLIGRA_VERSION_MAJOR '''x'''<br/>#define CALLIGRA_STABLE_VERSION_MINOR <b>y</b><br/>#define CALLIGRA_VERSION_RELEASE '''89 (Alpha)|91 (Beta)|92 (RC)'''<br/>#define CALLIGRA_ALPHA '''0|1|2|...'''<br/>#define CALLIGRA_BETA '''0|1|2|...'''<br/>#define CALLIGRA_RC '''0|1|2|...'''<br/>#define CALLIGRA_STABLE '''0|1'''<br/></tt>
* releases/#{version}-release.php
* Collect changelog items
* release notes translation:
* Collect screenshots
* send the release notes a few days before release to kde-i18n-doc at kde.org
* '''Write announcement for calligra.org'''
* complete the page "announcements/announce-#{version}.php" with link to the translation that are usually hosted on KDE i18n local team websites
** Ask for proofreading at kde-[email protected]
 
** See which packages will be ready at release day (*Linux, Windows, OSX), push people to have them ready
Last-minute changes:
* Set version tag in git repo to the commit the tarball is made from
* releases/index.php
* Add version for all Calligra bug.kde.org products
* announcements/index.php
* Major release:
* site.inc
**Create tour
* news.rdf
**Update stable major version at [http://community.kde.org/index.php?title=Template:Calligra/StableBranch&action=edit community.kde.org] and [http://userbase.kde.org/index.php?title=Template:Calligra/StableBranch&action=edit userbase.kde.org]
* menu.inc
**Update unstable major version at [http://community.kde.org/index.php?title=Template:Calligra/UnstableBranch&action=edit community.kde.org] and [http://userbase.kde.org/index.php?title=Template:Calligra/UnstableBranch&action=edit 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 [http://community.kde.org/index.php?title=Template:Calligra/Stable&action=edit community.kde.org] and [http://userbase.kde.org/index.php?title=Template:Calligra/Stable&action=edit userbase.kde.org]
* Update info in channel topic of #calligra and #kexi
* Update unstable stage at [http://community.kde.org/index.php?title=Template:Calligra/Stage&action=edit community.kde.org] and [http://userbase.kde.org/index.php?title=Template:Calligra/Stage&action=edit 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
*Publish news on [https://www.facebook.com/pages/Calligra/161929600510563 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]]

Latest revision as of 14:37, 29 January 2018

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}

(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

Maintainer of this section: Jstaniek (talk)