Am 06.12.2010 09:36, schrieb Jeroen Ruigrok van der Werven:
-On [20101206 08:30], "Martin v. Löwis" (email@example.com) wrote:
As a counter-example, I think the only way to phase out support for old OpenBSD releases is that we set a date.
If you want, I can provide you with specifics on the BSD platforms of what is currently in use, EOL and the future.
If that's publicly documented from a single starting page, having the URL of that page would be appreciated. Also, do users accept that policy? (i.e. would they feel sad if Python releases don't support BSD releases anymore that don't get patches?)
For Windows and Solaris, it seems that some users continue to use the system after the vendor stops producing patches, and dislike the prospect of not having Python releases for it anymore. However, they are in clear minority, so by our current policy for minority platforms (no need to support them), that's fine. This really triggered the "ten years" proposal: for quite some time now (20 years) people stop losing interest in operating systems after ten years.
Also, with regard to Windows 2000, XP and its APIs. Didn't XP already switch a bunch of APIs around that 2000 doesn't use? (Need to find that migration document.)
I don't understand the question: what does it meant to switch an API around? XP has added new API that wasn't available in 2000, if that's what you are asking.