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

  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 in the BRANCH

  7. update

  8. 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

  1. Update Windows Store package version and maxTestedVersion tag

    • packaging/windows/msix/manifest.xml

  2. 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. Get the tarball from gitlab:

  2. Unpack the tarball

  3. Run build-tools/ in the unpacked folder

  4. Package the tarball as .gz and .xz

  1. 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
  2. Upload tarballs to, where builders can pick them up:

Make Windows, Linux, macOS and Android packages

  1. Request four release builds on, 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 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 20(!) files in your release folder

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

    md5sum ./* > md5sum.txt
  8. Upload 21(!) files to (or ask sysadmins to do that using this manual

    • 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-Beta-x86_64.appimage.zsync (beta zsync belongs to /unstable/krita/updates/, stable to /stable/krita/updates/)


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



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


    • 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 (21 files) to
        * Source link:
        * Destination link:
        * There should be 16 files including `md5sum.txt`
    2) Add `Krita 4.2.9 Beta1` bugzilla version
  10. Now the folder on should have 21(!) files. Check if you missed something (and you surely did! :) ).

Release coordination

  1. Mail KDE release coordination <>

  2. Send release notes for future Krita versions to

  3. Create bugzilla version: Or file a sysadmin ticket for that.

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

PR and Communications


  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.


  1. Update download page

  2. Publish the announcement and release notes

  3. Add release links to Release History section of the site:

  4. Add the release to the file in MASTER.


  • tumblr (wolthera)

  • BlenderArtists (wolthera)

  • deviantart (wolthera)

  • VK (dmitry)

  • blendernation (boud)

  • twitter (boud)

  • facebook (boud)

  • 3dpro (boud)

  • reddit (raghukamath)


Additional info can be found here: