Re: [HACKERS] Packaging of postgresql-jdbc - Mailing list pgsql-jdbc

From Vladimir Sitnikov
Subject Re: [HACKERS] Packaging of postgresql-jdbc
Date
Msg-id CAB=Je-Epua7Bo0gOUMN2fdxC_+Y9bLQkRkDwm+yRn7dzjgeZSg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Packaging of postgresql-jdbc  (Álvaro Hernández Tortosa <aht@8kdata.com>)
Responses Re: [HACKERS] Packaging of postgresql-jdbc  (Álvaro Hernández Tortosa <aht@8kdata.com>)
Re: [HACKERS] Packaging of postgresql-jdbc  (Pavel Raiskup <praiskup@redhat.com>)
List pgsql-jdbc
Álvaro>    I think running tests is cool for the packaging process,
but is this needed for packaging? I mean, it's upstream who should run
them before releasing versions, right? :)

If you pick "upstream build artifact", you know it is tested.
If you use custom-made-kludge-patched build process, you'd better test
that new artifact before use.
It can easily fail in a unexpected way. For instance: not all ${...}
being replaced, not all the classes present, missing translations,
etc, etc.

Nothing personal. Just facts.

Vladimir


pgsql-jdbc by date:

Previous
From: Álvaro Hernández Tortosa
Date:
Subject: Re: [HACKERS] Packaging of postgresql-jdbc
Next
From: Álvaro Hernández Tortosa
Date:
Subject: Re: [HACKERS] Packaging of postgresql-jdbc