Making It Easier To Start Working On Bugzilla

[Wayne Mery]

On 12/20/2005 12:47 AM, Mick Weiss wrote:
>...
> - Another issue is that patches need to be maintained from version to 
> version, and some people submit a patch and then noone ever hears from 
> them again. I don't really have a solution for this, but I have seen 
> this with other projects. (I'm not sure if this is really an issue for 
> Bugzilla).

On a related note, ability to get a quicker snapshot of patch 
state/status patches might be a worthy goal. For example in 
https://bugzilla.mozilla.org/show_bug.cgi?id=319082 (a bug marked fixed 
so perhaps not an ideal example)

"patch, v2" has been reviewed.

was it checked in?
checked in for what versions?
backed out?
etc.

The status is not completely and immediately apparent by looking at the 
attachment information block unless someone has modified the 
attachment's name to indicate it's status (eg "patch, v2 checked in v2.20"]

Status information is often, as it should be, written in the comments. 
And bugzilla devs do an excellent good job of documenting what they have 
done (again, more consistently than some other products). But finding 
that information requires more reading.