GitLab

All repos that need it have their respective
  ecm_install_po_files_as_qm
  ki18n_install
  kdoctools_install
calls

https://mail.kde.org/pipermail/release-team/2022-May/012685.html

Heiko Becker authored Mar 04, 2022 and Albert Astals Cid committed Mar 04, 2022

https://mail.kde.org/pipermail/release-team/2022-February/012638.html

CCMAIL: release-team@kde.org

It was merged into kalarm

CCMAIL: release-team@kde.org

https://mail.kde.org/pipermail/release-team/2022-February/012605.html

CCMAIL: release-team@kde.org

https://mail.kde.org/pipermail/release-team/2022-January/012592.html

CCMAIL: release-team@kde.org

This reverts commit 0e0f62f7.

Plasma and Frameworks also sign their tags and I see no reason why the
Gear packages should be different.

(cherry picked from commit a013e5ed)

Having tons of local branches pushed to the main repo was not fun

Since
pim/zanshin@ed122f08

CCMAIL: release-team@kde.org

CCMAIL: release-team@kde.org

Heiko Becker authored Jul 30, 2021 and Albert Astals Cid committed Aug 07, 2021

For example rocs has
"project(rocs LANGUAGES CXX VERSION ${RELEASE_SERVICE_VERSION})"
in its CMakeLists. While being perfectly valid in cmake, it wasn't
matched by the regular expression.

(cherry picked from commit 8ee83569)

CCMAIL: release-team@kde.org

(cherry picked from commit c42556ed)

Arguably there's litte value to trigger a build after pushing a tag
because the commit the tag points to already triggered a build.
We could re-evaluate that if Gitlabs's CI takes over from Jenkin, but
for now I think it's best not to pollute the queue of the only builder
with meanigless jobs.

(cherry picked from commit a34f8542)