On Tuesday 13 June 2006 18:04, Olivier Goffart wrote: > Le mardi 13 juin 2006 02:23, Matt Rogers a écrit : > > Hi, > > > > I'm willing to spin a Kopete 0.12.1 if the bug count drops below 200 and > > stays there for about a week. I will check the bug count at least once a > > day, and once it drops below 200 and stays there for about 5 days, I'll > > start spinning a release. > > Ok, the bug count is now 200 at the time i write this email > > A Kopete release in fives days ? > > (considered the fact that i have noticed few jabber bug a could fix this > week) >
The bug count has to stay under 200 for five consecutive days before I start the release process. The questions is whether or not we want to release a Kopete 0.12.1 in a week. I'd rather wait awhile longer. I'm thinking the end of the June right now. > > Please note that I would still like for us to concentrate on KDE 4. There > > are a lot of things that need to get done for Kopete 1.0 (hopefully in > > KDE4. if it's not ready for 1.0, i won't call it 1.0) and the more we > > could work on them the better. > > I still don't feel comfortable with KDE4 > The problem with KDE4 is that i spend more time to compile than actually > coding. > thinks that work a day doesn't work anymore the next day. > > Exemple, the dbus introduction (which i am happy to finally see in > kdelibs) cause some issue. i spend lot of time to make knotify working > like before without even reach my wanted result > (because i'm not used to dbus yet) I completely understand your frustration and it doesn't help us break things and implement new stuff if we're fighting issues with other broken things. I've gone through the same thing with both KDevelop and Kopete, but in order to make KDE 4 great, we need to put lots of work into it. -- Matt _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
