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

List:       kde-core-devel
Subject:    Re: The case for a kdelibs 4.8
From:       todd rme <toddrme2178 () gmail ! com>
Date:       2011-09-30 12:58:26
Message-ID: CADb7s=tRq4fW-5fC62QrPznCOa6hesAQAOr_u2fA9AFC1_1QRQ () mail ! gmail ! com
[Download RAW message or body]

On Fri, Sep 30, 2011 at 10:07 AM, Aaron J. Seigo <aseigo@kde.org> wrote:
> On Thursday, September 29, 2011 14:01:50 Kevin Kofler wrote:
>> 2. It will be confusing to our users, and even to some packagers, to have a
>> KDE SC 4.8 on kdelibs 4.7. The rule so far has always been that the kdelibs
>> version must be the same as the KDE SC version.
>
> that's not a rule anymore, and hasn't been for a while now.
>
> other than the packaging specfile changes that seem to be required in the
> Fedora packages, i'm not sure what the real world confusion would be. when we
> release apps and workspace 4.8, we'll also do a platform 4.7.x release. the
> release communication will not say "SC 4.8" it will say "Platform 4.7, Plasma
> Workspaces 4.8 and application updates" (or something along those lines). that
> was not just a marketing ploy, but an attempt to align our public
> communication with the realities that already existed in KDE development.

I am not saying this is the best solution, I am just putting out as a
possible compromise.  Would it be possible to just call kdelibs 4.7.8
or whatever it ends up being "kdelibs 4.8", without adding any
significant new features?  I know you can, by KDE policy, add new
features at a x.x release, but is there any requirement that you have
to?  I know there are numerous other issues involved so this may be a
terrible idea.

-Todd
[prev in list] [next in list] [prev in thread] [next in thread]