--===============0454258754==
Content-Type: multipart/signed;
boundary="nextPart10801473.aC3qYv2bU9";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart10801473.aC3qYv2bU9
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 04 December 2005 17:15, Dan Kegel wrote:
> On 12/4/05, Kevin Krammer wrote:
> > > Great! Where are they documented? I do see the developer
> > > recommendations
> > > http://developer.kde.org/documentati...atibility.html
> > > but I don't see anything in e.g.
> > > http://developer.kde.org/development...s/release.html
> > > documenting what the policy is.
> > > For comparison, the Gnome "Release Planning" page,
> > > http://developer.gnome.org/dotplan/
> > > explicitly covers ABI stability policy.

> >
> > If nothing else, maybe you could add exactly what you wrote in your
> >
> > > email onto the kde site and link to it from the release planning
> > > page...

> >
> > Maybe better under http://developer.kde.org/policies/

>
> Yeah, but there has to be at least a pointer to it in
> the release planning page, I think.


A policy should always be followed, not just before a release.

But the check for binary compatability could be added

Cheers,
Kevin

=2D-=20
Kevin Krammer
Qt/KDE Developer, Debian User
Moderator: www.mrunix.de (German), www.qtforum.org

--nextPart10801473.aC3qYv2bU9
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBDk1binKMhG6pzZJIRAr7eAJ4xCEsQRjF8AImQZIub6V zkrEoTGwCffhWp
NnGbLcV+Be6t8fh3D+Ul+pA=
=gPs+
-----END PGP SIGNATURE-----

--nextPart10801473.aC3qYv2bU9--

--===============0454258754==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


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


--===============0454258754==--