[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: Including KDevelop in KDE Gear (for 21.12)
From:       Alexander Dymo <alex () alexdymo ! com>
Date:       2021-11-15 8:53:03
Message-ID: CABBcm41=uNOMBfRWsWCtaR-1q6x6oZMe_s6ukKGOczjW28pijQ () mail ! gmail ! com
[Download RAW message or body]

Well, KDevelop 4.0 was more than 2 years behind KDE 4.0. And like Sven
said, after 4.0 we preferred feature-heavy releases focused on getting new
functionality out as soon as it was ready.



On Fri, Nov 5, 2021 at 5:30 PM Jonathan Riddell <jr@jriddell.org> wrote:

> On Sat, 30 Oct 2021 at 09:36, Sven Brauch <mail@svenbrauch.de> wrote:
>
>> Hi,
>>
>> On 10/30/21 7:04 AM, Friedrich W. H. Kossebau wrote:
>> > Am Freitag, 29. Oktober 2021, 21:33:00 CEST schrieb Jonathan Riddell:
>> >> KDevelop did used to be part of the KDE SC releases and at some point
>> >> separated.  So one query is why did that release schedule separation
>> happen
>>
>> I looked in the archives and this seems to last have been the case for
>> KDevelop 3.3.x, released in 2006-ish, or maybe a bit later.
>>
>> This was > 15 years ago, completely different people working on a quite
>> different code base (the core C++ language support plugin was basically
>> completely rewritten *twice* since then!). So I'm not sure it makes
>> sense to be afraid of a potential ping-pong situation between being part
>> of KDE SC and not being part of it.
>>
>> Compared to 4.0 times, the project is now very mature and instead of
>> fast-paced feature development by a small core team, KDevelop's progress
>> is nowadays more a continuous stream of small fixes contributed by a big
>> crowd. So while releases used to be driven by the motivation of a few to
>> get new features out when they are done and then quickly follow-up with
>> stabilization releases, that is no longer the case.
>>
>
> Good answers :)
>
> Jonathan
>
>
>

[Attachment #3 (text/html)]

<div dir="ltr">Well, KDevelop 4.0 was more than 2 years behind KDE 4.0. And like Sven \
said, after 4.0 we preferred feature-heavy releases focused on getting new \
functionality out as soon as it was \
ready.<div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Fri, Nov 5, 2021 at 5:30 PM Jonathan Riddell &lt;<a \
href="mailto:jr@jriddell.org" target="_blank">jr@jriddell.org</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
dir="ltr">On Sat, 30 Oct 2021 at 09:36, Sven Brauch &lt;<a \
href="mailto:mail@svenbrauch.de" target="_blank">mail@svenbrauch.de</a>&gt; \
wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Hi,<br> <br>
On 10/30/21 7:04 AM, Friedrich W. H. Kossebau wrote:<br>
&gt; Am Freitag, 29. Oktober 2021, 21:33:00 CEST schrieb Jonathan Riddell:<br>
&gt;&gt; KDevelop did used to be part of the KDE SC releases and at some point<br>
&gt;&gt; separated.   So one query is why did that release schedule separation \
happen<br> <br>
I looked in the archives and this seems to last have been the case for <br>
KDevelop 3.3.x, released in 2006-ish, or maybe a bit later.<br>
<br>
This was &gt; 15 years ago, completely different people working on a quite <br>
different code base (the core C++ language support plugin was basically <br>
completely rewritten *twice* since then!). So I&#39;m not sure it makes <br>
sense to be afraid of a potential ping-pong situation between being part <br>
of KDE SC and not being part of it.<br>
<br>
Compared to 4.0 times, the project is now very mature and instead of <br>
fast-paced feature development by a small core team, KDevelop&#39;s progress <br>
is nowadays more a continuous stream of small fixes contributed by a big <br>
crowd. So while releases used to be driven by the motivation of a few to <br>
get new features out when they are done and then quickly follow-up with <br>
stabilization releases, that is no longer the \
case.<br></blockquote><div><br></div><div>Good answers \
:)</div><div><br></div><div>Jonathan</div><div><br></div><div>  </div></div></div> \
</blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread]