Hyrum K. Wright wrote:
> A couple of questions before I go volunteering:
> What is your typical work flow for managing the volume of patches that
> comes through the dev list? Do you just let the threads pile up in your
> inbox (or dev folder, etc.), or do you use some sort of external list?
> Any hints, for me or whoever else takes the position, would be great.
I apologize for being late with a response... the way I've been handling
the patches is to read the mailing list in Mozilla Thunderbird, saving
any message that contain a patch and marking the message as important.
I then use a Ruby script that reads the saved message, fetches a mailing
list archive URL, parses the message to get author, subject, etc. and
inserts a row into a MySQL database. I check the database to see
patches that have been sitting for a while, and I update the database if
a patch's status ever changes (e.g. it is applied or rejected). When a
patch has been sitting for long enough with no response, then I'll ping
the mailing list and add it to the issue tracker if there's still no
> How much time (on median) do you typically spend per week in the Patch
> Manager Role? Is it something on the order of a few minutes a day, or
> several hours a week?
Probably closer to a few minutes a day... when I was reading the mailing
list regularly, it was very easy to push patches through the process
described above. Once I started getting distracted by other things, it
turned into about an hour of work every three weeks or so, whenever I
caught up on reading the list. Speaking of which, I will catch up again
on any patches that have been posted in the past week, and will make the
Ruby script and a database dump available online. I'll post again when
By the way, I have no problem with either you or Kamesh taking over the
position, but I think it's probably not my decision to make. Any other
developers, what do you think?
Michael W Thelen
It is a mistake to think you can solve any major problems just with
potatoes. -- Douglas Adams
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Sep 8 02:08:33 2006