Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Tue, 18 Nov 2003 22:07:16 -0500 (Eastern Standard Time)
From: Joshua Slive <joshua@slive.ca>
To: dev@httpd.apache.org, trawick@attglobal.net
Subject: Re: Patch management
In-Reply-To: <3FB90190.8050408@attglobal.net>
Message-ID: <Pine.WNT.4.55.0311182201480.1544@RM505.mgmt.mcgill.ca>
References: <20031116091223.GA21639@netspace.org>
 <3FB7AFAE.5000509@attglobal.net>
 <1069003265.11280.292.camel@kepler> <20031117011037.406dcb6d.nd@perlig.de>
 <3FB90190.8050408@attglobal.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 17 Nov 2003, Jeff Trawick wrote:
> What must be done to the bug tracker we have now to track the patches better?
>
> (I'm not against having something better, but I don't want to see a delay in
> waiting for some magic tool.)
>
> We can already assign the keyword "PatchAvailable" for entries and mark entries
> as enhancements or bugs of various severities.  People with patches to submit
> can already manage the data entry themselves.

I did try to use the PatchAvailable keyword for a while.  I even posted
helpful links like this to the dev list:
http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Apache+httpd-1.3&product=Apache+httpd-2.0&keywords=PatchAvailable&keywords_type=anywords

I'm sure the people who skim the bug database traffic wouldn't mind making
sure that keyword gets assigned.

The biggest problem is:

> b) making sure the submitter gets some response in a reasonable time

Perhaps one thing to do would be to more strongly encourage people, as an
entry to apache development, to go through these PatchAvailable bugs, and
do formal reviews and tests of the code.  Of course a core team member
needs to do the final commit, but it is easier if there is evidence of
reviews.

Joshua.