On Thu, 2009-11-12 at 23:16 +0000, Greg Sabino Mullane wrote: > -----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?
If a business wants support they can buy it. There is no reason for this community to continue supporting it. > > > 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. > We can say 5 "years" from release though. Joshua D. Drake -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564 Consulting, Training, Support, Custom Development, Engineering If the world pushes look it in the eye and GRR. Then push back harder. - Salamander -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
