From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Stamp release 8.1.2. |
Date: | 2006-01-05 04:26:20 |
Message-ID: | 200601050426.k054QKY13472@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I thought about that again, and there are so many place to patch, where
> > do I do patches and where do I not? There is no clear line on what
> > should be stamped.
>
> Sure there is: what it says to do in RELEASE_CHANGES. There's no reason
> to turn that crank until we're just about ready to wrap.
You know how many places need to be changed for four releases? There
are a lot, and if we wait until the end, there is less time to check it.
We are more prone to error if we limit the time we can do stamping. It
seems easier to just stamp configure.in with a dummy commit message than
to bundle all this stuff for the end.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-01-05 05:15:52 | pgsql: Update release notes for 8.1.X, 8.0.X, 7.4.X, and 7.3.X. |
Previous Message | Tom Lane | 2006-01-05 04:23:56 | Re: pgsql: Stamp release 8.1.2. |