Moving KDevelop to Release service coverage?

[Sven Brauch]

Hi,

On 10/27/21 10:12 AM, Kevin Funk wrote:
> If plugin authors depend on an API feature from "58", just let them depend on
> KDevelop 21.12. Maybe above relation from yy.mm to SOVERSION could be
> persisted on the web page as well. Shouldn't be much work.

not sure if I'm being overly pragmatic here but historically, there have 
been very few KDevelop plugins developed outside of the core KDevelop 
circle. Especially, I do not remember any such plugin which was 
binary-packaged independently from KDevelop's development team and 
release schedule in the last decade.

So I'm honestly not sure if this question matters that much.

Oh, but of course this brings up another question: Would we want to move 
kdev-php and kdev-python to release service as well? I think that would 
make sense, no?

Greetings!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0xA4AAD0019BE03F15.asc
Type: application/pgp-keys
Size: 3139 bytes
Desc: OpenPGP public key
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20211028/56324761/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20211028/56324761/attachment.sig>