Do you want to track the translations from the 3.0 branches in their own branch then?

Yes if this makes the releaseme script work.

@jriddell @sitter IS it possible to get help on the tool? I am getting:

releaseme/tarme.rb --version 3.0.1 --origin stable --from-config kexi kexi
INFO -- ReleaseMe::Release: Getting source (git - kde:kexi [3.0])
INFO -- ReleaseMe::Release:  Getting translations...
INFO -- ReleaseMe::L10n: Downloading translations for kexi-3.0.1
WARN -- ReleaseMe::L10n: !!! No translations found at SVN path $lang/messages/calligra !!!
WARN -- ReleaseMe::L10n: Looked for templates: ["kexi.po", "keximigrate_mdb.po", "keximigrate_mysql.po", "keximigrate_odb.po", "keximigrate_postgresql.po", "keximigrate_spreadsheet.po", "keximigrate_sybase.po", "keximigrate_tsv.po", "keximigrate_xbase.po", "kexiforms_mapwidgetplugin.po", "kexiforms_webbrowserwidgetplugin.po"]

Tried also local config for releaseme - no luck, reported at https://bugs.kde.org/show_bug.cgi?id=377508

readme says:

Releaseme uses 'origins' to control which branch to release and where to draw translations from. An origin is basically the i18n association as configured in: https://phabricator.kde.org/source/sysadmin-repo-metadata/ It is imperative that you make sure the data configured there is correct and up to date!

I've found this update to the readme, @sitter. Nice that it's updated. My problem is inability to decipher what the 'correct configurations' would be. When I accepted recommendation for the releaseme tool as a one-click solution for tarballs I did not expect that simplicity of releaseme is at the cost of complexity of other requirements. I am assuming I am doing it completely wrong but would appreciate for a recipe specifically for kexi and kexi libs listed above. I've not found definitions for apps in releaseme.git/projects/ that I'd use as templates for my clearly typical case: a KDE app and some libs.

Another concern is hard to decipher error message of releaseme - pasted above and for the local version at https://bugs.kde.org/show_bug.cgi?id=377508. What the script 'thinks' the SVN path is? How it looked for templates? These are example questions users like me (who are not going to debug or read the ruby code) might have.

I'd very well delegate the task of managing translation files / infra to someone, it's second stable release already and the tarballs still have no automatically generated translations.

Waiting on releaseme maintainers. I'd suggest to restart the discussion on kdb, kproperty and kreport, we don't create stable i18n branches for kdereview, because it should be a temporary state *before* the release.

@ltoscano Ys, no hurry, kdereview first (95% of preparation is done).