Re: [HACKERS] 6.6 release

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, Vadim Mikheev <vadim(at)krs(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] 6.6 release
Date: 1999-12-13 02:44:20
Message-ID: 7399.945053060@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>>>> Ditto. Look at the 6_5 branch and you will see it was done far into the
>>>> 6.5 release, not at the 6.5.0 release. I don't want to continue
>>>> mentioning this for every release.
>>
>> The branch should be created on release, not after the release, else the
>> branch is useless...sorry, think I said something wrong
>> originally...didn't mean 'on beta', meant 'on release'...

> No.

Bruce is right: we should delay making a branch for REL7_0 patches
until people are ready to start committing new features for 7.1.
I'm guessing that would be a month or two after formal release of 7.0.
We did that after the 6.5 release (IIRC, we didn't make the branch
until around the time of 6.5.2) and I thought it worked just great;
saved a lot of double-patching.

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 1999-12-13 02:54:35 Re: [HACKERS] generic LONG VARLENA
Previous Message Bruce Momjian 1999-12-13 02:38:15 Re: [HACKERS] LONG