Dave Page wrote: > In my original message I described my thinking: > > - Developer submits patch, with additional info through a web interface. > > - The web interface formats an email containing the patch description, > patch and any other info entered, assigns it a patch number, and > forwards it to the patches list. > > - Discussion ensues on list as per normal. The tracking system monitors > the list and automatically attaches any posts to the patch that have the > appropriate reference in the subject line. > > - Community members and committers can review the entire discussion > through the systems web interface. Updated patches could be submitted > online. > > - Committers log into the system when necessary to alter the status > (committed, rejected, awaiting revision, under review etc), or the queue > name (8.3, 8.4 etc). This could also be done automagically via email > keywords from specific addresses. > > You would no longer need to manually manage the queue, and the > committers would simply need to tweak the status flag as required.
Sounds interesting, but I am not sure how that is going to track multiple versions of the patch, or changes in the email subject. The bottom line is that there is a lot of thinking that the patch queue is so large because no one knows what to do. "Oh, if we were better communicators, more would be done". The patch queue is large because we have lots of March 31 patches, and because we don't have enough people to review them quickly. The people who have expressed interest in reviewing patches already know where we stand on the patches, and a status email of where we are each patch will be posted shortly. I just can't do it this time because I am traveling. If you want to try a tracking system, go ahead, just pull from the patches email list, and somehow try to grab discussion from hackers/patches on this patches, and give a way to manually update the patch status via a web site. If your system works, I will not need to maintain a separate patches queue, but I will keep doing it until we know the web site idea will work, just in case. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend