From: | "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Maintenance Policy? |
Date: | 2009-07-11 02:37:00 |
Message-ID: | 20090710223700.72acae7b.darcy@druid.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 10 Jul 2009 19:51:31 -0400
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> > I'd suggest that we publish an official policy, with the following dates
> > for "EOL":
>
> I have no objection to setting an EOL date for 7.4 now, but I think it
> is premature to set EOL dates for later versions. I suppose the policy
> you have in mind here (but are not spelling out) is that versions will
> be EOL'd five years after release no matter what. I'm not convinced
How about "five (or four or...) years after the next version is
released?" That takes into account longer release schedules. That way
we aren't guaranteeing support for a hard term for a release but rather
that we will support it for a specified time from the date it is
superceded by the next version.
--
D'Arcy J.M. Cain <darcy(at)druid(dot)net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
From | Date | Subject | |
---|---|---|---|
Next Message | Theo Schlossnagle | 2009-07-11 04:02:27 | concurrent index builds unneeded lock? |
Previous Message | David E. Wheeler | 2009-07-11 01:05:59 | Re: Maintenance Policy? |