From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Dave Page <dpage(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL Release Support Policy |
Date: | 2009-12-05 20:33:42 |
Message-ID: | 21211.1260045222@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce pgsql-general pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> Could I request we change these dates slightly to
The intent of the policy is that the last formal minor release for a
branch will happen no earlier than the specified times. It might well
be later, since we're not going to schedule updates specially for this
--- it'd be whenever the next set of updates occur, and that would more
likely be driven by bugs in newer branches, not the oldest one.
In any case there's no need for someone to move off a version instantly
the day after the last release for it. So I really don't see why you
think there would be "panic updates". There's so much fuzz in when a
version would be effectively dead that a few months either way in the
nominal date wouldn't make any difference anyway.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-12-05 21:08:03 | Re: PostgreSQL Release Support Policy |
Previous Message | Simon Riggs | 2009-12-05 15:39:13 | Re: PostgreSQL Release Support Policy |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-12-05 20:35:39 | Re: tsvector from external files |
Previous Message | Merlin Moncure | 2009-12-05 20:10:48 | Re: Array comparison & prefix search |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-12-05 20:43:06 | Re: Reading recovery.conf earlier |
Previous Message | Ron Mayer | 2009-12-05 19:45:13 | Re: YAML Was: CommitFest status/management |