Re: 8.3.0 release schedule (Was:Re: [BUGS] BUG #3852: Could not create complex aggregate) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: 8.3.0 release schedule (Was:Re: [BUGS] BUG #3852: Could not create complex aggregate)
Date
Msg-id 10269.1199811059@sss.pgh.pa.us
Whole thread Raw
In response to Re: 8.3.0 release schedule (Was:Re: [BUGS] BUG #3852: Could not create complex aggregate)  (Magnus Hagander <magnus@hagander.net>)
Responses Re: 8.3.0 release schedule (Was:Re: [BUGS] BUG #3852: Could not create complex aggregate)  (Magnus Hagander <magnus@hagander.net>)
Re: 8.3.0 release schedule (Was:Re: [BUGS] BUG #3852: Could not create complex aggregate)  (Cédric Villemain <cedric.villemain@dalibo.com>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> On Tue, Jan 08, 2008 at 11:23:13AM -0500, Tom Lane wrote:
>> We didn't include 8.3RC1 in the security announcement because Josh
>> wanted to make a separate announcement for it, but from every
>> perspective except the PR one, it's out.

> There has been no annonucement whatsoever. Our web site stll claims beta4
> is the current version. I was under the impression that this tarball, like
> all others, are considered preliminary until announced one way or another.

Uh, no, that isn't the project policy.  If we were to find some fatal
problem in RC1 at this point, we'd spin an RC2, precisely because RC1
has been up on the servers for a couple days now and confusion would
inevitably result if we tried to redefine what RC1 was.

The lack of an announcement is not my bailiwick, but tarball-making
is.  Once a tarball appears in the public FTP directories, it's
official, and there's no reason to discourage people from using it.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: Dynamic Partitioning using Segment Visibility Maps
Next
From: Andrew Sullivan
Date:
Subject: Re: VACUUM FULL out of memory