Moving KDevelop to Release service coverage?

Milian Wolff mail at
Thu Oct 21 08:40:35 BST 2021

On Donnerstag, 21. Oktober 2021 00:32:39 CEST Friedrich W. H. Kossebau wrote:
> Am Donnerstag, 21. Oktober 2021, 00:11:19 CEST schrieb Sven Brauch:
> > On 10/20/21 8:22 PM, Friedrich W. H. Kossebau wrote:
> > > So, who would be in favour, who would not be in favour?
> > 
> > I think this is a very good idea, currently there are just small changes
> > happening in KDevelop mostly, which is very suitable for a
> > slow-and-steady release schedule. If you feel capable of taking care of
> > that, amazing :)
> And of course release team needs to approve this, though I could not think
> of any reason why KDevelop could not be part of KDE Gear.
> Thanks for reply, adding +1 to the list :)
> > If the AppImage would be generated automatically as well that would of
> > course be very good; do you know what would be required for that? We
> > kind of have an automated process which does everything already, or is
> > that too clunky?
> IIRC Milian has looked into getting binary factory working to also do
> AppImages for KDevelop, but still being in WIP state. He might give more
> details reading this :)
> That is principally also orthogonal to the release service/KDE Gear
> membership.

Basically we need to ensure that craft works for KDevelop and all its 
dependencies on Centos 7 and then integrate that into the new gitlab based CI.

See again:

This contains the central docker image that sets up craft in centos 7. We need 
to integrate that somehow into the gitlab CI, such that the craft cache can be 
shared. And it may be that some software needs to be fixed to allow building 
it on centos 7.


Milian Wolff
mail at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the KDevelop-devel mailing list