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

help / color / mirror / Atom feed
From: Greg Smith <gsmith@gregsmith.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Markus Wanner <markus@bluegap.ch>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Aidan Van Dyk <aidan@highrise.ca>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: Thu, 28 May 2009 15:12:43 -0400 (EDT)
Message-ID: <alpine.GSO.2.01.0905281348300.5408@westnet.com> (raw)
In-Reply-To: <11894.1243529112@sss.pgh.pa.us>
References: <10273.1243343651@sss.pgh.pa.us>
	<20090527212240.GP15213@yugib.highrise.ca>
	<603c8f070905271829i9458bdftcaed2dadb0a74583@mail.gmail.com>
	<20090528020909.GQ15213@yugib.highrise.ca>
	<603c8f070905271942ke9df2aah8648fe4d1228d43e@mail.gmail.com>
	<20090528125944.GS15213@yugib.highrise.ca>
	<603c8f070905280649m5d5fc458se54435dfe20cc7ca@mail.gmail.com>
	<4A1E9D98.7030208@dunslane.net>
	<8547.1243522369@sss.pgh.pa.us>
	<20090528174015.964447it00chy25b@mail.bluegap.ch>
	<603c8f070905280846q46220e39u57fc24ac7b6feb7@mail.gmail.com>
	<alpine.GSO.2.01.0905281203530.13556@westnet.com>
	<11894.1243529112@sss.pgh.pa.us>

On Thu, 28 May 2009, Tom Lane wrote:

> Each released minor version tag must check out the same as from CVS, at 
> least back to some specified point (perhaps 7.4.0).  I'd really prefer 
> to insist on that all the way back.

We'd all like to hope that conversion process that works for everything 
back to 7.4.0 would would also give useful results for all the old ones, 
too.  And it's worth testing as far back as possible.  I think it's just 
unrealistic to set the bar too high in the off chance that one of these 
old releases has something that's harder to fix than producing that 
version is worth.  That might be the case for some of the 7.1 stuff 
mentioned upthread for example.  If there are only a few stragglers that 
won't play nice, it might be easier to just publish a "git errata" list of 
those releases and move on.

In related news, I wanted to make it a bit easier to track followup on the 
whole "Action Item" list from the meeting.  I converted those to the 
standard format we were already using on the ToDo list, which provides a 
way to check off items that are done.  It may be worth breaking those out 
from the rest of the minutes, so that it's easier to extend them with 
things like these fleshed out git requirements.  Example: 
http://wiki.postgresql.org/wiki/PgCon_2009_Developer_Meeting#Source_Code_Management

Thoughts?

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD



view thread (74+ messages)  latest in thread

Message-ID: <alpine.GSO.2.01.0905281348300.5408@westnet.com>
Permalink:  ../alpine.GSO.2.01.0905281348300.5408@westnet.com/
Also on:    postgresql.org/message-id/alpine.GSO.2.01.0905281348300.5408@westnet.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: gsmith@gregsmith.com, tgl@sss.pgh.pa.us, robertmhaas@gmail.com, markus@bluegap.ch, andrew@dunslane.net, aidan@highrise.ca, heikki.linnakangas@enterprisedb.com, magnus@hagander.net
  Subject: Re: PostgreSQL Developer meeting minutes up
  In-Reply-To: <alpine.GSO.2.01.0905281348300.5408@westnet.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