From: Tom Lane <tgl@sss.pgh.pa.us>
To: The Hermit Hacker <scrappy@hub.org>
Cc: D'Arcy J.M. Cain <darcy@druid.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Re: [ANNOUNCE] Announce: Release of PyGreSQL version 3.0
Date: Sat, 07 Oct 2000 23:38:32 -0400
Message-ID: <19712.970976312@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.BSF.4.21.0010072112560.1627-100000@thelab.hub.org>
References: <Pine.BSF.4.21.0010072112560.1627-100000@thelab.hub.org>
The Hermit Hacker <scrappy@hub.org> writes:
> On Thu, 5 Oct 2000, Tom Lane wrote:
>> darcy@druid.net (D'Arcy J.M. Cain) writes:
>>>> When is 7.1 being locked down? I may be releasing 3.1 with a few small
>>>> fixes and changes very soon.
>>
>> You've probably got about 2 weeks before beta starts. Bug fixes are
>> accepted during beta freeze, of course --- just no new-feature
>> development.
> how are we dealing with third party software like this though? Stuff like
> PyGreSQL and PGAccess should be "at the authors discretion", no? As they
> don't interfere with the core functionality and build of the system?
Well, a third party author always has the option to release his code
separately on whatever timeline seems good to him. But I think that for
third-party code included in the distribution, the same standards ought
to apply as for the Postgres code itself: we don't want people sticking
alpha-quality code into a Postgres release tarball, whether it's core
functionality or not. It's not as if "no new features for a month" is
a particularly onerous standard to meet ;-)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, scrappy@hub.org, darcy@druid.net, pgsql-hackers@postgresql.org
Subject: Re: Re: [ANNOUNCE] Announce: Release of PyGreSQL version 3.0
In-Reply-To: <19712.970976312@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox