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 <j...@jriddell.org> wrote: > On Sat, 30 Oct 2021 at 09:36, Sven Brauch <m...@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 > > >