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

List:       kde-release-team
Subject:    Re: Yakuake releases
From:       Nate Graham <nate () kde ! org>
Date:       2019-06-22 14:18:16
Message-ID: b708e897-e86a-f6c8-582f-7a9a7a3a77c1 () kde ! org
[Download RAW message or body]

Yeah, one of the things I like about KDE Applications is that nothing 
contained within it can ever gets forgotten like this. It's not a 
panacea, of course, but we never run into a situation where an app that 
was once actively developed but has lost its development resources goes 
for a long time with no release because there's no longer an active 
maintainer to request it.

This automatic release process strikes me as a very desirable feature.


Nate



On 6/22/19 3:55 PM, Andreas Sturmlechner wrote:
> Hi,
> 
> as a packager I would appreciate more releases of not only yakuake.
> That does not necessarily mean moving all to KDE Applications is the
> solution, certainly not all of them...
> 
> When I look at what else I need to carry around patches for:
> calligra - 20kB worth of patches just to build against moderately
> recent poppler versions and even Qt 5.11
> calligraplan - also patch for Qt 5.11 and qca detection
> kdesvn - needs backport from 2.0 branch for Qt 5.11
> krename - only git master currently builds against exiv2-0.27, which
> has been around for more than a year
> plasma-redshift-control - fix for redshift-1.12 is only in git master
> skanlite - last release 10 months ago, cmake fixes and hidpi support
> in git master since April
> 
> Regards,
> Andreas
> 
> On Wed, 19 Jun 2019 at 18:55, Nate Graham <nate@kde.org> wrote:
>>
>> Hello everyone,
>> I notice that Yakuake's last release was 15 months ago. What do people
>> think about getting it added to the KDE Applications bundle so that it
>> gets auto-released on a regular basis? This might help to attract more
>> contributors, among other benefits.
>>
>> Nate
>>

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