-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
>> needs significant preparation for them. Announcing an EOL early in time >> would give them the required time before the version used disappears. > > So, should we announce it for June? No, it should be longer. June is practically around the corner as far as business planning is concerned. Make it a year. Since it's mid November, why not just say 2011? > And yes, i'm +1 for having a rule for EOL, like "5 versions are > supported". If we released on a consistent schedule, this *might* be possible. But we don't, so we can't say something like this. - -- Greg Sabino Mullane g...@turnstep.com PGP Key: 0x14964AC8 200911121815 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkr8lykACgkQvJuQZxSWSsi6xACdHU7xKgsfG+/zE2StXp97mdjC XGoAn3LvIjzh1RKmD9K0Zyrg9W3LuHxt =jCVo -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
