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

List:       kopete-devel
Subject:    Re: [Kopete-devel] Maintaining BC
From:       Olivier Goffart <ogoffart () tiscalinet ! be>
Date:       2003-08-30 20:41:41
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le Samedi 30 Août 2003 22:32, vous avez écrit :
> On Saturday 30 August 2003 20:48, Olivier Goffart wrote:
> > I never did api before, libkopete is the first api I maintain, and even
> > the first real program i do. So I don't know what is good API or not, I
> > can judge only by comparing with the kdelibs or QT api, or the old one.
>
> The point is that the actual changes towards BC aren't that hard to make
> once you know what to do. Implementing a new API isn't hard either.
>
> The difficult part, that takes time, thought, experience and again TIME is
> getting an API to stabilize and mature. 

The api didn't realy change since the kopeteaccount port.
and i see that it is almost perfect.
preuve: almost no changes since there

libkopete is realy stable. there are not real bug against libkopete, now that 
all the UI is go away outside libkopete.

> Go over each method. Look at it.
> Compare it with API docs. Apply unit tests on them. Check code for awkward
> algorithms that are in need of refactoring, etc.

this has already been done.
our apidoc make sence now.

> This is the reason why I dare saying that it is completely impossible to
> have a proper BC API that is not only BC but also maintainable and
> sustaible within 6 months.

6 months *without* new big features

> We have a quite nice API now, but it still has issues. Some of them known,
> some deeply hidden behind the lack of attention. Before declaring libkopete
> BC we need to look at and address all these issues. This takes time.

why? Kopete 1.0 may be BC even with a bad API., that's not a problem currently 
since kopete 1.0 will not live logner than 2 year. and without new big 
features.

i even would like to jump to Kopete 4.0 for KDE 4.0 to sync the numbers 
version (that make sence since release are done in the same time)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/UQwKz58lY8jWrL0RAnz8AJ4xV6DupESfxunEzT76vqUbcgiKWgCePnjI
BNOjybWMDevpNWHi/u0MUHg=
=VYea
-----END PGP SIGNATURE-----

_______________________________________________
Kopete-devel mailing list
Kopete-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kopete-devel

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