From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dave Page <dpage(at)pgadmin(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Maintenance Policy? |
Date: | 2009-07-07 16:06:10 |
Message-ID: | FC162818-B3B0-4C12-9F58-2CFEA727E61D@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jul 7, 2009, at 8:06 AM, Tom Lane wrote:
> I'd personally be perfectly happy with a community decision to
> desupport
> 7.4 now, or perhaps after the next set of update releases (which we're
> probably overdue for, BTW). We cannot support an indefinitely large
> set
> of back branches, and a five-year lifespan seems about right to me.
I had kind of thought it was five active versions, which translates to
more or less the same thing. In that case, 7.4 would shortly be
dropped. So I ask:
1. Should 7.4 be dropped after the release of 7.4.26?
2. Should there be an articulated, published maintenance policy? Or,
at least, a prominent list saying, "these are the versions we actively
support as of now"?
Thanks,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2009-07-07 16:10:02 | Re: *_collapse_limit, geqo_threshold |
Previous Message | David E. Wheeler | 2009-07-07 16:02:53 | Re: 8.3 PLpgSQL Can't Compare Records? |