Re: 8.3 pending patch queue - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: 8.3 pending patch queue
Date
Msg-id E1539E0ED7043848906A8FF995BDA57901A35D0A@m0143.s-mxs.net
Whole thread Raw
In response to Re: 8.3 pending patch queue  (Bruce Momjian <bruce@momjian.us>)
Responses Re: 8.3 pending patch queue
List 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


pgsql-hackers by date:

Previous
From: "Andrew Dunstan"
Date:
Subject: Re: [BUGS] BUG #2873: Function that returns an empty set
Next
From: markwkm@gmail.com
Date:
Subject: patch auto-processing prototype