Making a release

Before the release

  1. Coordinate with #kde-promo

  2. Notify translators of string freeze!

  3. Verify that the release notes page is done, like https://krita.org/en/krita-4-2-release-notes/

  4. Verify that all 8 (eight!) dependency builds are up to date. Remember that these builds are built from master, not from the stable branch.

Update version in source code

  1. !! REMOVE THE SURVEY LINK !! (or, if this is a beta, make a survey and update the survey link)

  2. update the version of krita.xmlgui

  3. update the CMakeLists.txt version

  4. update the snapcraft.yaml file

  5. update the appstream screenshots

  6. update org.kde.krita.appdata.xml ‘s release tag

  7. update create_tarball’s config.ini

  8. update download_release_artifacts.sh

  9. update Android version (keep in mind that all Krita releases on Android are marked as Beta at the moment):

    • packaging/android/apk/AndroidManifest.xml

    • packaging/android/apk/build.gradle

  10. When releasing beta-version double-check that you updated to “beta1”, not just plain “beta”. Only “alpha” versions can be made without a number, because they are built nightly.

Update versions in the stable branch to avoid XMLGUI conflicts

  1. stable branch is always marked as “alpha” (without a number in the end)

  2. update the version of krita.xmlgui; it should be $(( $VERSION_IN_RELEASE_BRANCH + 1 ))

  3. update the CMakeLists.txt version

  4. update org.kde.krita.appdata.xml ‘s release tag

  5. packaging/android/apk/AndroidManifest.xml

Create the tarball

Create and push the tag

  1. Set the tag:

    git tag -a v4.2.9-beta1 -m "Krita 4.2.9 Beta1"

  2. Push the tag:

    git push origin refs/tags/v4.2.9-beta1:refs/tags/v4.2.9-beta1

  3. If you need to change the tag position (not recommended):

    # remove the previous tag

git push origin :refs/tags/v4.2.9-beta1

# make a new tag locally
git tag -a v4.2.9-beta1 -m "Krita 4.2.9 Beta1"

# push the new tag
git push origin refs/tags/v4.2.9-beta1:refs/tags/v4.2.9-beta1

# all Krita developers now have to refetch tags to
# get the updated tag position
git fetch origin --tags

Create the tarball

  1. Go into the ./packaging/ folder, check that the version in ‘config.ini’ file reflects the right tag and version number. It should look like that:

    [krita]
gitModule   = yes
gitTag      = v4.2.9
category    = graphics
mainmodule  = branches/stable
l10nmodule  = krita
version     = 4.2.9
translations= yes
docs        = no
kde_release = no

  2. Create the tarball:

    ./create_tarball_kf5.rb -n -a krita

  3. Check that created archive has ‘po’ folder and it actually has translations

  4. Sign both tarballs:

    gpg --output krita-4.2.9-beta1.tar.gz.sig --detach-sign krita-4.2.9-beta1.tar.gz
gpg --output krita-4.2.9-beta1.tar.xz.sig --detach-sign krita-4.2.9-beta1.tar.xz

  5. Upload tarballs to files.kde.org, where builders can fpick them up:

Make Windows, Linux, OSX and Android packages

  1. Request four release builds on binary-factory.kde.org, after starting each build,go to “Console Output” section, click on “Input Requested” and choose a tarball version to build.

  2. Download all built artifacts using download_release_artifacts.sh script. Open the script and modify KRITA_VERSION variable to correspond to the version string.

  3. For each build check:

    • Krita starts

    • Localization works

    • Python plugins are available

    • Basic painting and most recently fixed bugs are fixed

  4. Sign both AppImages:

    gpg --detach-sign --output krita-4.2.9-beta-x86_64.appimage.sig krita-4.2.9-beta-x86_64.appimage
gpg --detach-sign --output gmic_krita_qt-x86_64.appimage.sig gmic_krita_qt-x86_64.appimage

  5. Sign four Android packages (or send them to Boud for signing)

    • krita-arm64-4.2.9-beta1-unsigned.apk

    • krita-arm32-4.2.9-beta1-unsigned.apk

    • krita-x86-4.2.9-beta1-unsigned.apk

    • krita-x86_64-4.2.9-beta1-unsigned.apk

    After signing, remove “-unsigned” suffix, so the signed packages would look like that:

    • krita-arm64-4.2.9-beta1.apk

    • krita-arm32-4.2.9-beta1.apk

    • krita-x86-4.2.9-beta1.apk

    • krita-x86_64-4.2.9-beta1.apk

  6. Now you should have 19(!) files in your release folder

  7. Generate an md5sum.txt file for all of them:

    md5sum ./* > md5sum.txt

  8. Upload these files to download.kde.org (or ask sysadmins to do that using this manual ftp://upload.kde.org/README):

    • krita-4.2.9-beta1.tar.gz

    • krita-4.2.9-beta1.tar.gz.sig

    • krita-4.2.9-beta1.tar.xz

    • krita-4.2.9-beta1.tar.xz.sig

    • gmic_krita_qt-x86_64.appimage

    • gmic_krita_qt-x86_64.appimage.sig

    • krita-4.2.9-beta1-x86_64.appimage

    • krita-4.2.9-beta1-x86_64.appimage.sig

    • krita-x64-4.2.9-beta1-dbg.zip

    • krita-x64-4.2.9-beta1-setup.exe

    • krita-x64-4.2.9-beta1.zip

    • krita-4.2.9-beta1.dmg

    • krita-arm64-4.2.9-beta1.apk

    • krita-arm32-4.2.9-beta1.apk

    • krita-x86-4.2.9-beta1.apk

    • krita-x86_64-4.2.9-beta1.apk

    • md5sum.txt

  9. Template ticket for sysadmins:

    Hi, sysadmins!

Could you please do the final steps for publishing Krita release?

There are two tasks:

1) Upload release artifacts (20 files) to download.kde.org:

    * Source link: https://files.kde.org/krita/release-4.2.9-beta1/
    * Destination link: https://download.kde.org/unstable/krita/4.2.9-beta1/
    * There should be 16 files including `md5sum.txt`

2) Add `Krita 4.2.9 Beta1` bugzilla version

  10. Now the folder on download.kde.org should have 20(!) files. Check if you missed something (and you surely did! :) ).

Release coordination

  1. Mail KDE release coordination <release-team@kde.org>

  2. Send release notes for future Krita versions to news@publisher.ch

  3. Create bugzilla version: https://bugs.kde.org/editversions.cgi?product=krita Or file a sysadmin ticket for that.

  4. [only for a major release] Warn kde sysadmins that we’re going to release and that krita.org is going to take load. Just file a ticket on phabricator.

PR and Communications

Pre-release

  1. Update Kiki page

  2. Update press pack and page

  3. Verify if manual pages are updated, if not annoy @woltherav and add undocumented features to Krita: Manual

  4. Notify people that they can start making release demonstrations.

Release

  1. Update download page

  2. Publish the announcement and release notes

  3. Add release links to Release History section of the site: https://krita.org/en/about/krita-releases-overview/

Post-release

  • tumblr (wolthera)

  • BlenderArtists (wolthera)

  • deviantart (wolthera)

  • VK (dmitry)

  • blendernation (boud)

  • twitter (boud)

  • facebook (boud)

  • 3dpro (boud)

  • reddit (raghukamath)

Notes

Additional info can be found here: https://phabricator.kde.org/T10762