tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Freeze question - PyGreSQL

"D'Arcy J.M. Cain" <> writes:

> On Tue, 01 Jan 2013 12:19:25 -0500
> Greg Troxel <> wrote:
>> It depends - is this a leaf package?  The point of the 'no changes to
>> non-leaf packages' notion is that such changes trigger a rebuild of
>> many packages in bulk builds, and these builds are what tells us
>> what's wrong and what needs to be fixed.  So without a low-churn
>> situation, it's hard to ensure overall quality, even if the
>> churn-causing updates are themselves 100% correct.
> Hmm.  The package databases/py-pgnotify depends on it.  Not sure if it
> has unit tests or not.  PyGreSQL is thick with unit tests.

Well, if there is only one dependency, it seems ok to update; that's
pretty close to zero compared to 50.

>> (And are you sure 4.1 is ok (and builds on all platforms where the
>> previous builds, more or less), and users are better served with it vs
>> the previous?  That depends on a lot of things not immediately
>> apparent to people not really familiar with py-postgresql, but it
>> sounds like you are perhaps the one of us who is familiar).
> It builds and passes the unit tests on Linux, Windows and, of course,
> NetBSD.  Not sure about anything else but the unit tests do give us a
> lot of comfort in that area.
> Yes, I,, am very familiar with it.  :-)

Then it seems reasonable to update.

Attachment: pgpxTIsD3XAy4.pgp
Description: PGP signature

Home | Main Index | Thread Index | Old Index