Drawy 1.0.0 Release | Request for Support

Julius Künzel julius.kuenzel at kde.org
Mon May 4 11:17:08 BST 2026


Hi Prayag,

it is not a big deal, others did the some mistake before. Best would be to do a 1.0.1 release. The metainfo file is not only relevant for Flathub, but other consumers too. As soon as files are uploaded to download.k.o they should not be replaced anymore.

Regards,
Julius Künzel
KDE Developer
Matrix: @jlskuz:kde.org
KDE GitLab: https://invent.kde.org/jlskuz

04.05.2026 00:29:35 Prayag Jain <prayagjain2 at gmail.com>:

> Hi Team,
> 
> Drawy is a new KDE whiteboard application that has approached its first release 1.0.0. I'm writing this email because of an oversight from my end during the release process.
> 
> During the release process, I used releaseme[https://invent.kde.org/sdk/releaseme] to create a tag in the git repository on invent[https://invent.kde.org/graphics/drawy] and a tarball which was just uploaded to download.kde.org[http://download.kde.org] a few hours ago (https://phabricator.kde.org/T18625). I realised that I missed an important part of the release process, which was updating the appstream metainfo file. As a result, the uploaded tarball uses an outdated version of the file which contains outdated description, no screenshots, no keywords, and no release information which are required by software repositories like FlatHub.
> 
> I deeply regret this oversight and would like to understand how I can proceed from here. Should I create a new tag *1.0.1* and upload a new tarball with the updated files or would it be better to request for the removal of the currently uploaded tarball, delete the tag, and proceed again? The first option seems like the way to go but I'm still not sure because *1.0.0* has not been announced yet.
> 
> I deeply apologize for the inconvenience caused and will appreciate your support as I'm still figuring some things out.
> 
> Thanks and Regards,
> Prayag Jain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260504/02e41bff/attachment.htm>


More information about the release-team mailing list