| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(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 17:03:45 |
| Message-ID: | 20150608170345.GG24173@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 8, 2015 at 12:32:45PM -0400, David G. Johnston wrote:
> On Mon, Jun 8, 2015 at 12:14 PM, Geoff Winkless <pgsqladmin(at)geoff(dot)dj> wrote:
>
> On 8 June 2015 at 17:03, Claudio Freire <klaussfreire(at)gmail(dot)com> wrote:
>
> It's not about the 5 minutes of compile time, it's about the
> signalling.
>
> 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.
>
>
> I can see that, and can absolutely get behind the idea of a nightly being
> flagged as an alpha, since it should involve next to no developer time.
>
>
>
> Nightly where? This is an international community.
The daily snapshot tarballs are built in a way to minimize the number of
development tools required:
http://www.postgresql.org/ftp/snapshot/dev/
These would be easier to use than pulling from git.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-06-08 17:06:31 | Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |
| Previous Message | Alvaro Herrera | 2015-06-08 17:01:52 | Re: [CORE] back-branch multixact fixes & 9.5 alpha/beta: schedule |