From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Aidan Van Dyk <aidan@highrise.ca>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: Tue, 26 May 2009 12:18:17 -0400
Message-ID: <13461.1243354697@sss.pgh.pa.us> (raw)
In-Reply-To: <4A1C11D5.4070406@dunslane.net>
References: <937d27e10904270840vaf70c0fr37518478b31d8a15@mail.gmail.com>
<4A189843.3010200@agliodbs.com>
<20090524165012.GL8123@tamriel.snowman.net>
<4A1A52F5.7030009@hagander.net>
<20090525122821.GO8123@tamriel.snowman.net>
<4A1BABBC.7070803@hagander.net>
<4A1BE039.70008@dunslane.net>
<10273.1243343651@sss.pgh.pa.us>
<4A1BFF70.4000506@dunslane.net>
<20090526144812.GC15213@yugib.highrise.ca>
<12570.1243351182@sss.pgh.pa.us>
<4A1C11D5.4070406@dunslane.net>
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> Up to now I've always been of the opinion that fixing those tags wasn't
>> worth taking any risk for. But if we are thinking of moving away from
>> CVS, then this clearly becomes one of the hurdles we have to jump on the
>> way.
> I think we need just to remove the two tags in question (they have long
> been irrelevant). Prudence suggests that we should do that some time
> (weeks, I think) after the 8.4 release, when reverting ,if we find any
> breakage, won't be too painful.
I don't see a lot of point in waiting till after 8.4.0. There is no
time, ever, where we are sure there will be no release for weeks ---
a security or data-loss bug could crop up at any time. And not messing
up back branch update releases is even more important than not messing
up 8.4.0, because the back branches are much more likely to get dropped
straight into production.
Obviously we want a solid backup of the pre-modification CVS repository,
and we have to follow Aidan's advice about synchronizing the change with
mirror repositories, but I don't see a strong argument for waiting weeks
to do this. I think we should get it over with, so people can get on
with the work that it's blocking.
regards, tom lane
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: tgl@sss.pgh.pa.us, andrew@dunslane.net, aidan@highrise.ca
Subject: Re: PostgreSQL Developer meeting minutes up
In-Reply-To: <13461.1243354697@sss.pgh.pa.us>
* 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