[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:       Jonathan Riddell <jr () jriddell ! org>
Date:       2021-10-29 19:33:00
Message-ID: CANX=XXPVQ_f78JCGg4EfhrK+9h8+bkJu+XH7Y5_81s3hSf9wfA () mail ! gmail ! com
[Download RAW message or body]

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
and would it happen again?

Jonathan


On Fri, 29 Oct 2021 at 16:52, Friedrich W. H. Kossebau <kossebau@kde.org>
wrote:

> Hi,
>
> we would like to switch KDevelop from its own release schedule to KDE
> Gear,
> starting with 21.12. This includes the following repositories:
>
> * https://invent.kde.org/kdevelop/kdevelop
> * https://invent.kde.org/kdevelop/kdev-python
> * https://invent.kde.org/kdevelop/kdev-php
>
> This switch to have schedule finding and basic release work provided by
> the
> good release team workers is to deal with current KDevelop contributors
> rather
> looking at writing code than planning releases, and should then restore a
> continuous stream of fixes and improvements to the users. And with some
> packagers also help with reaction time on new releases, as they now can
> plan
> for the whole year.
>
> While KDevelop and the Python & PHP support plugins should be rather
> mature,
> please still given them a quick sanity check whether the KDevelop bubble
> has
> not developed too far from what could be considered standard in other KDE
> Gear
> apps.
>
> Cheers
> Friedrich
>
>
>

[Attachment #3 (text/html)]

<div dir="ltr"><div>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 \
and would it happen again?</div><div><br></div><div>Jonathan</div><div><br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 29 Oct 2021 at 16:52, \
Friedrich W. H. Kossebau &lt;<a \
href="mailto:kossebau@kde.org">kossebau@kde.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">Hi,<br> <br>
we would like to switch KDevelop from its own release schedule to KDE Gear, <br>
starting with 21.12. This includes the following repositories:<br>
<br>
* <a href="https://invent.kde.org/kdevelop/kdevelop" rel="noreferrer" \
                target="_blank">https://invent.kde.org/kdevelop/kdevelop</a><br>
* <a href="https://invent.kde.org/kdevelop/kdev-python" rel="noreferrer" \
                target="_blank">https://invent.kde.org/kdevelop/kdev-python</a><br>
* <a href="https://invent.kde.org/kdevelop/kdev-php" rel="noreferrer" \
target="_blank">https://invent.kde.org/kdevelop/kdev-php</a><br> <br>
This switch to have schedule finding and basic release work provided by the <br>
good release team workers is to deal with current KDevelop contributors rather <br>
looking at writing code than planning releases, and should then restore a <br>
continuous stream of fixes and improvements to the users. And with some <br>
packagers also help with reaction time on new releases, as they now can plan <br>
for the whole year.<br>
<br>
While KDevelop and the Python &amp; PHP support plugins should be rather mature, <br>
please still given them a quick sanity check whether the KDevelop bubble has <br>
not developed too far from what could be considered standard in other KDE Gear <br>
apps.<br>
<br>
Cheers<br>
Friedrich<br>
<br>
<br>
</blockquote></div>



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