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

List:       kde-devel
Subject:    Re: Backporting/switching a plugin for 4.2.1?
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2009-01-28 14:06:37
Message-ID: 200901280706.38133.aseigo () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Wednesday 28 January 2009, Harald Hvaal wrote:
> Is this possible? Or will the current implementation have to be maintained
> until 4.3?

bug fixes may be backported, but not new features or string changes.

this is an odd sort of change however, because is it a bug fix or is it a 
feature? larger changes in the code base tend to come with commensurately 
higher risk to the stability.

so... my input would be: if it makes you more efficient and it doesn't 
introduce new features or strings, then put it into trunk and maybe backport 
it for 4.2.1 or 4.2.2 once those of us using trunk/ have had the chance to 
hammer away on it and prove it. if you have unit tests for it, even better.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software


["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


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