This is the easiest method, but you'll have to remove and plug your device back in before you can use SuperDisplay again.

Select Transfer files as the USB mode from the system notification that pops up after plugging in your device (see image).Publish the announcement and release notesĪdd release links to Release History section of the site: Īdd the release to the .xml file in MASTER.If you wish to transfer files with between your device after installing SuperDisplay, you have two options:

Notify people that they can start making release demonstrations. Verify if manual pages are updated, if not annoy and add undocumented features to Krita: Manual Warn kde sysadmins that we’re going to release and that is going to take load. chĬreate bugzilla version: Or file a sysadmin ticket for that. Send release notes for future Krita versions to news. Verify that the previous version of Krita AppImage can update to Check if you missed something (and you surely did! :) ). Now the folder on should have 21(!) files. Packaging/android/apk/AndroidManifest.xmlĬreate the tarball ¶ Create and push the tag ¶Ĭould you please do the final steps for publishing Krita release?ġ) Upload release artifacts (20 files) to :Ģ) Upload updates ZSync artifacts (1 file) to :ģ) Add `Krita 5.1.0 Beta1` bugzilla version Update the version of krita.xmlgui it should be $(( $VERSION_IN_RELEASE_BRANCH + 1 )) Stable branch is always marked as “alpha” (without a number in the end)

Update versions in the stable branch to avoid XMLGUI conflicts ¶ Only “alpha” versions can be made without a number, because they are built nightly. When releasing beta-version double-check that you updated to “beta1”, not just plain “beta”. Update Android version (keep in mind that all Krita releases on Android are marked as Beta at the moment): packaging/android/apk/adle !! REMOVE THE SURVEY LINK !! (or, if this is a beta, make a survey and update the survey link)

Git fetch origin & git log origin / master 3 rdparty

Krita android