From pidgin-devel  Wed Mar 26 16:41:14 2008
From: John Bailey <rekkanoryo () rekkanoryo ! org>
Date: Wed, 26 Mar 2008 16:41:14 +0000
To: pidgin-devel
Subject: Re: Summer of Code
Message-Id: <47EA7CAA.1050302 () rekkanoryo ! org>
X-MARC-Message: https://marc.info/?l=pidgin-devel&m=120654969506142
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============4258246647230639562=="

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============4258246647230639562==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig31FDD9D02A8F48AF070FA746"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig31FDD9D02A8F48AF070FA746
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Luke Schierer wrote:
> Basically, Redhat is the only one I know actually *supporting* software=

> after the upstream has dropped it.  We are, thanks to Stu's efforts,
> doing something lesser, we are worrying about if our software works wit=
h
>  obsolete libraries.

Ok, this makes sense and answers my question quite well.

> My thought was, how long are those obsolete libraries supported by
> _anyone_?  From that I hoped to derive an idea of how long it is
> reasonable to assume a meaningful number of people are using a given
> obsolete library version, and thus how long we might want to think abou=
t
> it.

Following the other branch that discusses the timeframes, 3 years does se=
em a
reasonable timeframe to support an obsoleted library version.  If we were=
 to
adopt that now, it would obviously cause some chaos to ensue.  However, a=
s Stu
indirectly suggested, it is something we could definitely do once we go t=
o 3.0.0
and move forward from there.

> It seems to me that after a given span, we're sort of encouraging peopl=
e
> not to update their system by enabling them to continue using "new"
> software on it.

I agree entirely.

John


--------------enig31FDD9D02A8F48AF070FA746
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iD8DBQFH6nyqBWJH/emdNtsRAtCyAJ0RFNZ6o7OW6mYVfNp5Sw0ITJmE+gCfR6nh
nCOkfCmyabTq2QuZBrPd1aA=
=6o8F
-----END PGP SIGNATURE-----

--------------enig31FDD9D02A8F48AF070FA746--


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

_______________________________________________
Devel mailing list
Devel@pidgin.im
http://pidgin.im/cgi-bin/mailman/listinfo/devel

--===============4258246647230639562==--