pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Marc G. Fournier <scrappy@hub.org>
Cc: 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: Sun, 8 Oct 2000 00:02:00 -0400 (EDT)
Message-ID: <200010080402.AAA02394@candle.pha.pa.us> (raw)
In-Reply-To: <Pine.BSF.4.21.0010072353490.9375-100000@hub.org>

> > 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 ...

Yes, that is true.  I don't have a problem with 3rd party stuff that
does not install by default.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



view thread (12+ messages)  latest in thread

Message-ID: <200010080402.AAA02394@candle.pha.pa.us>
Permalink:  ../200010080402.AAA02394@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200010080402.AAA02394@candle.pha.pa.us

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: pgman@candle.pha.pa.us, scrappy@hub.org, tgl@sss.pgh.pa.us, darcy@druid.net, pgsql-hackers@postgresql.org
  Subject: Re: Re: [ANNOUNCE] Announce: Release of PyGreSQL version 3.0
  In-Reply-To: <200010080402.AAA02394@candle.pha.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