[Kopete-devel] Post 3.2 Kopete and packagers

[Helio Chissini de Castro]

C'mon guys, be reasonable...

I was making packages since early 3.2 development stage..
I made almost 100 releases of packages, polishing our insane splitted 
structure, and even create some upgrade structures.
I moved efforts to release KDE as main interface on next Conectiva again, 
despite the industry now pushing Gnome and of course Kopete would be the main 
client messenger.

So now for a not so reasonable thing, you decide move to another group set ? I 
will need lost all my jobs on those modules and start again on kdenetwork and 
kdeextragear packages ? verify all upgrades problems from our last two 
releases again ? Move the test team test all set of packages AGAIN ?
Before someone try to say "IT'S JUST ONE PACKAGE MOVING", me and my coleague 
have to handle more than 200 packages, so a long time planning was needed. 
And include on this a overchrged test team.
And of course, as a signal of immaturity, peolpe here could make me put licq 
on front again and make kopete a third part release..

This is exactly we don't need now, after have all press talking about since 
beta 1 as Kopete great addition, a thing that makes we are losting control 
and giving more reasons to "suite oriented guys" questioning the use of KDE.

-- 
Helio Chissini de Castro
KDE Developer
Development - Conectiva S.A.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20031125/54b84659/attachment.sig>