Re: Re: [ANNOUNCE] Announce: Release of PyGreSQL version 3.0

> > 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,
Pennsylvania19026