| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
| Cc: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [CORE] Restore-reliability mode |
| Date: | 2015-06-08 16:16:34 |
| Message-ID: | CAKFQuwYg5-kKVvibUK4gLeKyWn370FoPYJ7Z=Za=iu+a-9VXOw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 8, 2015 at 12:03 PM, Claudio Freire <klaussfreire(at)gmail(dot)com>
wrote:
> Just *when* is git ready for testing? You don't know from the outside.
>
> I do lurk here a lot and still am unsure quite often.
>
> Even simply releasing an alpha *tarball* would be useful enough. What
> is needed is the signal to test, rather than a fully-built package.
>
>
IIUC the master branch is always ready for testing.
I do not think the project cares whether everyone is testing the exact
same codebase; as long as test findings include the relevant commit hash
the results will be informative.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2015-06-08 16:32:45 | Re: [CORE] Restore-reliability mode |
| Previous Message | Geoff Winkless | 2015-06-08 16:14:27 | Re: [CORE] Restore-reliability mode |