Re: PostgreSQL Release Support Policy - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PostgreSQL Release Support Policy
Date
Msg-id 21211.1260045222@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL Release Support Policy  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: PostgreSQL Release Support Policy  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.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


pgsql-hackers by date:

Previous
From: Ron Mayer
Date:
Subject: Re: YAML Was: CommitFest status/management
Next
From: Tom Lane
Date:
Subject: Re: Reading recovery.conf earlier