I updated the bug tracker.

Anything related to building/compiling is now marked with the prefix 'Build issue: '. I modified the priority of a few. Most build issues are now tagged with Blocker, Critical, or Major, although there are other build issues rated lower.

Possibly I missed a few. Please check your own reports and add the 'Build issue: ' prefix as necessary.

With these updates, we now know which bug reports are build issues. Just search for 'Build issue: '. No need for an etherpad. :)

A check box would be nice. Does bugzilla support that?

http://bugs.pearsoncomputing.net/bugzilla/bugzilla/bugzilla/buglist.cgi?quicksearch=%22Build+issue%3A+%22

How many? 72 reports of build issues. Yet remember that many reports are similar --- resolve one report and resolve several.

Not necessarily related to build issues, there are 30 bug reports with attached patches. If we seek a way to triage the bug tracker, I recommend first focusing on Blocker reports, then Critical, then Major, etc., but within each priority, first address those with patches.

http://bugs.pearsoncomputing.net/bugzilla/bugzilla/bugzilla/bugzilla/buglist.cgi?bug_status=PATCHAVAIL&query_format=advanced&order=bug_severity%2Cshort_desc%20DESC%2Cbug_id%20DESC&query_based_on=

I will push patches to GIT but often I need technical review and approval. Sometimes one person is sufficient but other times more when I believe a "root cause analysis" is required, such as reverting patches. As project leader, Tim is an exception and when he says push I'll push.

Tim,

Unless I can do this on my own, would you please add my email address to the bug tracker notification list? That way I'll know about new bug reports and can quickly tag any new report as a build issue if needed. I then can post to this list any such new reports.

Darrell