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

help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: 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 13:00:26 -0400
Message-ID: <20150608170026.GU26667@tamriel.snowman.net> (raw)
In-Reply-To: <CAKFQuwYg5-kKVvibUK4gLeKyWn370FoPYJ7Z=Za=iu+a-9VXOw@mail.gmail.com>
References: <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>
	<CAKFQuwYg5-kKVvibUK4gLeKyWn370FoPYJ7Z=Za=iu+a-9VXOw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

David,

* David G. Johnston (david.g.johnston@gmail.com) wrote:
> On Mon, Jun 8, 2015 at 12:03 PM, Claudio Freire <klaussfreire@gmail.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.

For my 2c, I do believe it's useful for projects which are based on PG
or which work with PG to have a 'alpha1' tag to refer to.  Asking users
to test with git hash XYZABC isn't great.  Getting more users of
applications which use PG to do testing is, in my view at least, a great
way to improve our test coverage and I do think having an alpha will
help with that.

That said, I'm not pushing to have one released this week or before
PGCon or any such- let's get the back-branch releases dealt with and
then we can get an alpha out.

	Thanks!

		Stephen

Attachments:

  signature.asc (application/pgp-signature, 818B) download

view thread (79+ messages)  latest in thread

Message-ID: <20150608170026.GU26667@tamriel.snowman.net>
Permalink:  ../20150608170026.GU26667@tamriel.snowman.net/
Also on:    postgresql.org/message-id/20150608170026.GU26667@tamriel.snowman.net

 · 

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: sfrost@snowman.net, david.g.johnston@gmail.com, klaussfreire@gmail.com, pgsqladmin@geoff.dj
  Subject: Re: [CORE] Restore-reliability mode
  In-Reply-To: <20150608170026.GU26667@tamriel.snowman.net>

* 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