Re: Release cycle length

Marc G. Fournier wrote:
> On Tue, 18 Nov 2003, Peter Eisentraut wrote:
>
> > 0. As you say, make it known to the public. Have people test their
> > in-development applications using a beta.
>
> and how do you propose we do that? I think this is the hard part ...
> other then the first beta, I post a note out to -announce and -general
> that the beta's have been tag'd and bundled for download ... I know Sean
> does up a 'devel' port for FreeBSD, but I don't believe any of the RPM/deb
> maintainers do anything until the final release ...
>
> > 1. Start platform testing on day 1 of beta. Last minute fixes for AIX
> > or UnixWare are really becoming old jokes.
>
> then each beta will have to be "re-certified" for that beta, up until
> release ... doable, but I don't think you'll find many that will bother
> until we are close to release ...
>
> > 2. Have a complete account of the changes available at the start of beta,
> > so people know what to test.
>
> Bruce, when do you do your initial HISTORY file? Something to move to the
> start of beta, if not?

I see beta starting on:

revision 1.277
date: 2003/08/04 22:30:30; author: pgsql; state: Exp; lines: +3 -3

change tag to 7.4beta1 and update the Copyright to 2003

Guess what folks? We are now in Beta!!

and 7.4 HISTORY updated on:

revision 1.196
date: 2003/08/03 23:26:05; author: momjian; state: Exp; lines: +324 -26
Update HISTORY file for 7.4.

so the HISTORY file was updated the day before beta started. I haven't
always been good about this, but I am now.

--
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