| From: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: 8.3 pending patch queue |
| Date: | 2007-01-09 17:12:41 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA57901A35D0A@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > I'm confused, I thought the difference between the pgpatches queue
and
> > the pgpatches_hold queue is the release the patch is targeted for.
If
> > there's a third queue for patches that need review before being
added to
> > another queue, could we have that visible somewhere, so that we know
> > what's in it?
>
> Well, sort of. During 8.2 feature freeze the 8.2 hold queue was for
> 8.3, and the patches queue was for 8.2, but once we started 8.3, they
> were both for 8.3.
So wouldn't it be easier to always move the hold queue into the patches
queue
asap when the new dev cycle begins (the patches queue is naturally empty
when we release, because patches have been applied or moved to the hold
queue) ?
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | markwkm | 2007-01-09 17:18:09 | patch auto-processing prototype |
| Previous Message | Csaba Nagy | 2007-01-09 16:48:24 | Re: Autovacuum Improvements |