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

help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Jim Nasby <Jim.Nasby@bluetreble.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: pgsql-core <pgsql-core@postgresql.org>
Subject: Re: [CORE] postpone next week's release
Date: Mon, 01 Jun 2015 11:09:31 -0700
Message-ID: <556C9FDB.3010508@agliodbs.com> (raw)
In-Reply-To: <WM!e24a585d68f2f809c2322b600e229c89045b8a04bf067c5d4320f8bedccd95093872b0a43b010e2747e9edd82dd2a7b9!@asav-3.01.com>
References: <20150529195751.GN26667@tamriel.snowman.net>
	<27697.1432929660@sss.pgh.pa.us>
	<CA+Tgmoadg9dHLpWodfwDaTZ=RbW+C_4CrgYyZ=Vx5QpMyP=N5A@mail.gmail.com>
	<28477.1432931820@sss.pgh.pa.us>
	<20150529210459.GH26863@alap3.anarazel.de>
	<20150529211224.GF16602@momjian.us>
	<5000.1432935433@sss.pgh.pa.us>
	<20150529222800.GG16602@momjian.us>
	<556C8454.5070409@BlueTreble.com>
	<25637.1433176341@sss.pgh.pa.us>
	<20150601163443.GB9491@awork2.anarazel.de>
	<26465.1433177780@sss.pgh.pa.us>
	<WM!e24a585d68f2f809c2322b600e229c89045b8a04bf067c5d4320f8bedccd95093872b0a43b010e2747e9edd82dd2a7b9!@asav-3.01.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

All,

Just my $0.02 on PR: it has never been a PR problem to do multiple
update releases, as long as we could provide a good reason for doing so
(like: fix A is available now and we didn't want to hold it back waiting
for fix B).

It's always a practical question of (a) packaging and (b) deployment.
That is, we can get packager fatigue where some updates don't get
packaged, and we can get user fatigue where they start ignoring updates.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


-- 
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 (78+ messages)  latest in thread

Message-ID: <556C9FDB.3010508@agliodbs.com>
Permalink:  ../556C9FDB.3010508@agliodbs.com/
Also on:    postgresql.org/message-id/556C9FDB.3010508@agliodbs.com

 · 

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: josh@agliodbs.com, tgl@sss.pgh.pa.us, andres@anarazel.de, Jim.Nasby@bluetreble.com, bruce@momjian.us, robertmhaas@gmail.com, sfrost@snowman.net, magnus@hagander.net, pgsql-core@postgresql.org
  Subject: Re: [CORE] postpone next week's release
  In-Reply-To: <556C9FDB.3010508@agliodbs.com>

* 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