On Mon, Sep 12, 2011 at 10:50, Gavin Flower <GavinFlower@xxxxxxxxxxxxxxxxx> wrote: > On 12/09/11 20:44, Magnus Hagander wrote: >> >> On Mon, Sep 12, 2011 at 10:40, Gavin Flower >> <GavinFlower@xxxxxxxxxxxxxxxxx> wrote: >>> >>> On 12/09/11 20:31, Magnus Hagander wrote: >>>> >>>> On Mon, Sep 12, 2011 at 10:10, Toby Corkindale >>>> <toby.corkindale@xxxxxxxxxxxxxxxxxxxx> wrote: >>>>> >>>>> http://www.postgresql.org/docs/9.1/static/release-9-1.html >>>>> contains the line: >>>>> "Release Date: 2011-09-12" >>>>> >>>>> *bounces excitedly* >>>>> >>>>> Has the release candidate gone final today? >>>> >>>> Not yet. But we are planning to put it out, and we need to load the >>>> website documentation ahead of time. >>>> >>> Then how come was put on the download page over 24 hours ago? >> >> We always put the files up on the ftpsite some time ahead to make sure >> it hits all the mirrors. It's not officially released (and guaranteed) >> until you see the announcement. >> > So there is a probability (presumably very small) that the source may change > - if a significant problem is discoved late in the process, but one that can > be quickly fixed? Yes. > More interesting: how likely is the source to change, and what are the > general guidelines associated with such a change? It has happened once or twice in the past, but very seldom. What happens is the version is removed again, a fix is applied, and a re-release is done with a new version number. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
