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

List:       kde-core-devel
Subject:    Re: hard-dep for Qt 4.8
From:       todd rme <toddrme2178 () gmail ! com>
Date:       2012-01-18 9:11:58
Message-ID: CADb7s=sfXGxi=fixX4Si5GvyJQ_8WKvsbMTi6Lrnt0bTCoQf9g () mail ! gmail ! com
[Download RAW message or body]

On Wed, Jan 18, 2012 at 8:54 AM, Thomas Zander <zander@kde.org> wrote:
> On Wednesday 18 January 2012 06.35.57 Martin Gr=E4=DFlin wrote:
>> I didn't say that this is a reason. I wanted to highlight the problem of
>> not =A0depending on 4.8 and everybody using 4.8. I'm not going to start
>> reviewing code for "is this a Qt 4.8 change".
>
> Martin,
>
> if you remember there are a lot of people using KDE that are not 'core'
> developers. Typically they are one-time developers, they are artists, the=
y are
> translators etc.
> I just wanted to point this out since your attitude can easily be mistake=
n as
> not caring about the people that are not able to do the Qt upgrade. I do
> believe you care, and thats why I think its important to indeed put in th=
at
> little bit of extra time to make sure we don't use Qt4.8 APIs. =A0 Or jus=
t
> respond fast to a person noticing the compilation issue.
>
> Its not a whole lot of effort, as far as I can tell, but it does have a p=
retty
> big influence on our community members that may not have the computer pow=
er or
> computer savy or just the time you have.
>
> thanks :)

But according to Martin, this isn't just about API changes, it is also
about behavior changes.  How do you expect people to know if they are
relying on a Qt 4.8-specific behavior?

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