-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
>> I'm not sure how useful that is. Surely while we encourage people to run
>> a recent major version, we also want to encourage people who will not
>> or cannot upgrade to at least be running the latest revision of a branch,
>> no matter how old it is?
> We don't support 7.3. Not even if you run the latest version.
No, but I imagine we still would encourage people to run the latest revision
of it. Come this time next year, I hope that we'll tell people on 7.4.2 to
upgrade to 9.0 as soon as possible, but to upgrade to 7.4.27 *immaediately*.
>> How about a compromise? We add a new field to that XML so we can state
>> that it is unsupported, but leave it in there. That way, programs such
>> as check_postgres can not only distinguish between old but valid versions
>> and invalid versions (e.g. "7.typo.oops") but can act in a more intelligent
>> way for unsupported versions. Heck, maybe an estimated end-of-life date
>> field for all versions as well?
> How do you add that field in a backwards compatible way? Meaning that
> people or tools relying on it should *not* see 7.3 or 6.1 or whatever.
> And it needs to be done within the RSS spec (which does allow custom
> namespaces though, so that may not be a problem)
Well I don't know what people are reading the XML, so let's discuss tools.
Do you have a use case in mind where adding old versions would break something?
Has this always been advertised as a list of *supported* versions, or as a list
of the *latest* revisions? I've always assumed the latter was more important
that the former.
> As for an estimated end-of-life, yes, we could definitely add that.
> Now that we finally have it :-)
+1
>> Either way, please add 7.4 back in. :)
>
>Done, will be on in the next site rebuild.
Thanks much, and thanks to Devrim for originally spotting the bug.
- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201002010931
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAktm5hIACgkQvJuQZxSWSshVwwCeINTRgE7L5UWHJBIJgKDq3GIe
X/gAoOivHWlQaVI3nI+TWjUkwxTlicUx
=d+Yp
-----END PGP SIGNATURE-----
