| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Álvaro Hernández Tortosa <aht(at)8kdata(dot)com> |
| Cc: | Pavel Raiskup <praiskup(at)redhat(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org>, Matteo Melli <matteom(at)8kdata(dot)com>, Pavel Kajaba <pkajaba(at)redhat(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, hhorak(at)redhat(dot)com |
| Subject: | Re: [HACKERS] Packaging of postgresql-jdbc |
| Date: | 2016-02-17 17:43:50 |
| Message-ID: | CAB=Je-Epua7Bo0gOUMN2fdxC_+Y9bLQkRkDwm+yRn7dzjgeZSg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2016-02-17 17:48:21 | Re: [patch] Proposal for \crosstabview in psql |
| Previous Message | Peter Geoghegan | 2016-02-17 17:27:01 | Re: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Hernández Tortosa | 2016-02-17 17:49:20 | Re: [HACKERS] Packaging of postgresql-jdbc |
| Previous Message | Álvaro Hernández Tortosa | 2016-02-17 17:25:30 | Re: [HACKERS] Packaging of postgresql-jdbc |