[Kopete-devel] Post 3.2 Kopete and packagers

[Rob Kaper]

On Tue, Nov 25, 2003 at 06:24:35PM +0100, Stephan Kulow wrote:
> You're talking major releases here. There is no reason why the protocol
> handling code shouldn't be updated in a stable branch when the protocol
> changes. 

May I take that liberty for Atlantik and monopd? ;-)

(Actually I haven taken that liberty in 3_1_BRANCH without complaints and
I'm very careful monopd protocol changes are compatible with older clients,
monopd CVS sends tons of duplicate messages just for backwards
compatibility.)

But note, I control monopd releases so I can more easily time these changes.
In the case of Kopete, it could occur that a plugin for a proprietary
protocol needs to be changed immediately to keep functioning. Giving the
time needed for a KDE bugfix release and the unavoidable discussions whether
such a protocol change justifies triggering a new KDE bugfix release when
required ahead of schedule, I'd say there's a very good argument not to put
those plugins in kdenetwork.

I'd still like the Kopete instant messaging core to be released as part of
KDE though.

Rob
-- 
Rob Kaper     | "In the name of sheer pity, won't someone operate on
cap at capsi.com | Chairman Arafat and put that poor cancer into a cleaner
www.capsi.com | environment? -- Rick Brookhiser
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20031125/37834fdf/attachment.sig>