Zeugswetter Andreas ADI SD wrote: > > > > 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) ?
The hold queue has patches that still need discussion, or ideas for patches, so it is more than just patches ready for application, and moving the whole thing at once would overwhelm patch reviewers. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
