pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marc G. Fournier <scrappy@hub.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
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, 7 Oct 2000 23:55:09 -0400 (EDT)
Message-ID: <Pine.BSF.4.21.0010072353490.9375-100000@hub.org> (raw)
In-Reply-To: <19712.970976312@sss.pgh.pa.us>

On Sat, 7 Oct 2000, Tom Lane wrote:

> 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 ;-)

agreed about the alpha quality, but if someone like D'Arcy or Constantin
releases a new version of their code, is there any reason to hold off on
bringing that in?  Haven't we done that in the past with pgaccess as it
is?  I seem to recall Bruce bringing in a new release of PgAccess close to
the release, but am not 100% certain of this ...





view thread (12+ messages)  latest in thread

Message-ID: <Pine.BSF.4.21.0010072353490.9375-100000@hub.org>
Permalink:  ../Pine.BSF.4.21.0010072353490.9375-100000@hub.org/
Also on:    postgresql.org/message-id/Pine.BSF.4.21.0010072353490.9375-100000@hub.org

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-docs@postgresql.org
  Cc: scrappy@hub.org, tgl@sss.pgh.pa.us, darcy@druid.net, pgsql-hackers@postgresql.org
  Subject: Re: [ANNOUNCE] Announce: Release of PyGreSQL version 3.0
  In-Reply-To: <Pine.BSF.4.21.0010072353490.9375-100000@hub.org>
  References: <19712.970976312@sss.pgh.pa.us> <Pine.BSF.4.21.0010072353490.9375-100000@hub.org>

* 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