pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: David Gould <daveg@sonic.net>
To: Claudio Freire <klaussfreire@gmail.com>
Cc: Geoff Winkless <pgsqladmin@geoff.dj>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [CORE] Restore-reliability mode
Date: Mon, 8 Jun 2015 16:02:21 -0700
Message-ID: <20150608160221.437fb596@engels> (raw)
In-Reply-To: <CAGTBQpbxxr==+LB9FntOEx59KfWR7B8qTRDeyYyyNw574dqt+Q@mail.gmail.com>
References: <CA+TgmoYovkev0xXnxaTD8vnt=M9Cn+RmOkVEouqwj6_9JLkzLw@mail.gmail.com>
	<CANP8+jK3v=KW1tE8Dz4TKsRZdWiG7r2yfAmFb6rAQvCTfY=Hpg@mail.gmail.com>
	<20150605162012.GQ133018@postgresql.org>
	<CANP8+jLr6B+U766-5K0HRZV39kz6MG-HzhZNmo58cuoXDjhWPg@mail.gmail.com>
	<CABUevExFm8E=+YSbYbCys67jobaY+gUAR19Mh4kMhQaVuupd0w@mail.gmail.com>
	<1433586450.6239.20.camel@gunduz.org>
	<CAEzk6fc6YiyRNMTHnam6ishGSFScvMNk-=ytFdYsceRcw3bV9Q@mail.gmail.com>
	<CAH7T-apL5ddcj3Qu=3hH3ObJUPKpHG7c2Rr_ndDV4HNoYRSbcg@mail.gmail.com>
	<CAEzk6ffGP5ZyCj7QsnT4y5JAYr+b37L6STpQM_2sRd9DnWkp1w@mail.gmail.com>
	<CAMkU=1wusmcyQkx=SAANz9S8PQu=MsD6T+QNxMvNsPm0UtgSjA@mail.gmail.com>
	<20150608055950.4435a734@engels>
	<CAEzk6fc-B9Hen_65w1KOYRPuN7r_NxZmhi9E6Z85YgQ0g4foZw@mail.gmail.com>
	<CA+TgmoYLpagRhvDEwN57FNrbFHo=VRikJLr+s-ajuhbUfs190Q@mail.gmail.com>
	<CAEzk6ffspLDFuQJLaB8exoC9wGVOTYie8xy3As7HoGE6PYA96w@mail.gmail.com>
	<CAGTBQpbxxr==+LB9FntOEx59KfWR7B8qTRDeyYyyNw574dqt+Q@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On Mon, 8 Jun 2015 13:03:56 -0300
Claudio Freire <klaussfreire@gmail.com> wrote:

> > Ohmygosh, you have to rpm install a bunch of -devel stuff? What a massive
> > hardship.
> 
> 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.

This. The clients I referred to earlier don't even use the rpm packages,
they build from sources. They need to know when it is worthwhile to take a
new set of sources and test. Some sort of labeling about what the contents
are would enable them to do this.

I don't think a monthly snapshot would work as well as the requirement is
knowing that "grouping sets are in" not that "it is July now".

-dg

-- 
David Gould                                    daveg@sonic.net
If simplicity worked, the world would be overrun with insects.


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (79+ messages)  latest in thread

Message-ID: <20150608160221.437fb596@engels>
Permalink:  ../20150608160221.437fb596@engels/
Also on:    postgresql.org/message-id/20150608160221.437fb596@engels

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: daveg@sonic.net, klaussfreire@gmail.com, pgsqladmin@geoff.dj
  Subject: Re: [CORE] Restore-reliability mode
  In-Reply-To: <20150608160221.437fb596@engels>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox