Message: previous - next
Month: April 2012

Re: [trinity-devel] Bug tracker update

From: Slávek Banko <slavek.banko@...>
Date: Tue, 17 Apr 2012 03:01:15 +0200
On Tuesday 17 of April 2012 00:36:15 Darrell Anderson wrote:
> 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?
> 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.
> 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

Good job, Darell.

has "build issue" in the text, but not in the subject. Is this correct?