Joshua D. Drake wrote: > > > I don't have a concrete proposal to make, but I do think that the > > current patch-queue process is not suited to the project as it stands > > today. Maybe if this issue-tracking stuff gets off the ground, we > > could let developers place ACK or NAK flags on patches they've looked > > at, and have some rule about ACK-vs-NAK requirements for something to go > > in. > > How about *requiring* test cases that prove the patch?
That doesn't hit most of the failures, which can be portability, performance, or missing features, or bad style. -- 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 4: Have you searched our list archives? http://archives.postgresql.org
