| From: | Thomas Swan <tswan(at)idigx(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Two weeks to feature freeze |
| Date: | 2003-06-21 04:03:01 |
| Message-ID: | 3EF3D8F5.10606@idigx.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
>
>
>>It would be nice to have a system which could receive a patch and
>>compile and verify that it passes the tests before it goes to Bruce's
>>queue; or compile on multiple platforms to check for portability
>>problems, for example.
>>
*snip*
>Another point is that passing on one platform doesn't ensure passing on
>another. Here we really rely on the willingness of the pghackers
>community to update to CVS tip regularly and run the regression tests
>when they do. Again, tests that take a couple minutes to run are ideal;
>if they took a week then the uptake would drop to zero, and we'd not be
>ahead.
>
>
Have you considered something similar to the Mozilla tinderbox approach
where you have a daemon checkout the cvs, compile, run regression tests,
and report a status or be able to report a status?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dann Corbit | 2003-06-21 04:03:40 | Re: Two weeks to feature freeze |
| Previous Message | Tom Lane | 2003-06-21 03:57:43 | Re: Two weeks to feature freeze |