Date: Mon, 8 Jun 2015 05:59:50 -0700
From: David Gould <daveg@sonic.net>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Geoff Winkless <pgsqladmin@geoff.dj>, Pg Hackers
 <pgsql-hackers@postgresql.org>
Subject: Re: [CORE] Restore-reliability mode
Message-ID: <20150608055950.4435a734@engels>
In-Reply-To: 
 <CAMkU=1wusmcyQkx=SAANz9S8PQu=MsD6T+QNxMvNsPm0UtgSjA@mail.gmail.com>
References: 
 <CA+TgmoYovkev0xXnxaTD8vnt=M9Cn+RmOkVEouqwj6_9JLkzLw@mail.gmail.com>
 <20150603135049.GA74753@tornado.leadboat.com>
 <WM!4ae914f9770e3cb63aa899dbc2db60d7ff4a3ad580e90f3dc1cd72315fff26fd1935dbe8884fd2e9f5370d881036c3bd!@asav-3.01.com>
 <556F3798.6010707@agliodbs.com>
 <CANP8+jJPyQLadtqrPJKrBVOEvK85nz+2oMk=CDAcUrwS-O-eNA@mail.gmail.com>
 <CA+TgmoYP=7XNn-9O+2Z8fuRahVxGVuHkkp3ZUxCsHeCD7GTpHA@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


I think Alphas are valuable and useful and even more so if they have release
notes. For example, some of my clients are capable of fetching sources and
building from scratch and filing bug reports and are often interested in
particular new features. They even have staging infrastructure that could
test new postgres releases with real applications. But they don't do it.
They also don't follow -hackers, they don't track git, and they don't have
any easy way to tell if if the new feature they are interested in is
actually complete and ready to test at any particular time. A lot of
features are developed in multiple commits over a period of time and they
see no point in testing until at least most of the feature is complete and
expected to work. But it is not obvious from outside when that happens for
any given feature. For my clients the value of Alpha releases would
mainly be the release notes, or some other mark in the sand that says "As of
Alpha-3 feature X is included and expected to mostly work."

-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