16 Apr
2012
16 Apr
'12
3:36 p.m.
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?qui…
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/buglis…
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
16 Apr
16 Apr
4:18 p.m.
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.
Tim,
A long while back we added a empty email address to every single bug
report, one that automagically is on the email list of all new bugs as
well. I think the idea was that this email account would forward to some
sort of list that people could subscribe to and receive bug reports from
all bugs. Obviously that would only be a few developers who are
sufficiently interested.
What say you? Can we do this?
Calvin
9:36 p.m.
New subject: [trinity-devel] Re: Bug tracker update
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.
Tim,
A long while back we added a empty email address to every single bug
report, one that automagically is on the email list of all new bugs as
well. I think the idea was that this email account would forward to some
sort of list that people could subscribe to and receive bug reports from
all bugs. Obviously that would only be a few developers who are
sufficiently interested.
What say you? Can we do this?
Calvin
9:55 p.m.
New subject: [trinity-devel] Re: Bug tracker update
Yes we can. It's a good idea and I need to figure
out
how to set it up.
If you don't see progress please remind me via Email--things
are hectic here but I would like to get this feature in place.
How about we also reconfigure the system such that when people use the simple search text
box at the top, that results include resolved bug reports as well? Currently a simple
search excludes resolved reports.
Typical usage is for people to query the system before filing a bug report. When the
system ignores resolved reports the person then believes no bug report has been filed and
files a new report. Although these options are available in the advanced search features,
we should not expect casual users to use advanced features.
Simple search is handy. We just need to include resolved reports too. :)
Darrell
10:08 p.m.
New subject: [trinity-devel] Re: Bug tracker update
Yes we can.
It's a good idea and I need to figure out
how to set it up.
If you don't see progress please remind me via Email--things
are hectic here but I would like to get this feature in place.
How about we also reconfigure the system such that when people use the
simple search text box at the top, that results include resolved bug
reports as well? Currently a simple search excludes resolved reports.
Typical usage is for people to query the system before filing a bug
report. When the system ignores resolved reports the person then believes
no bug report has been filed and files a new report. Although these
options are available in the advanced search features, we should not
expect casual users to use advanced features.
Simple search is handy. We just need to include resolved reports too. :)
Darrell
17 Apr
17 Apr
4:18 a.m.
On 04/17/2012 12:55 AM, Darrell Anderson wrote:
I can probably do this, changing the default search shouldn't be
difficult to edit.
Calvin
Yes we can.
It's a good idea and I need to figure out
how to set it up.
If you don't see progress please remind me via Email--things
are hectic here but I would like to get this feature in place.
How about we also reconfigure the system such that when people use the simple search text
box at the top, that results include resolved bug reports as well? Currently a simple
search excludes resolved reports.
Typical usage is for people to query the system before filing a bug report. When the
system ignores resolved reports the person then believes no bug report has been filed and
files a new report. Although these options are available in the advanced search features,
we should not expect casual users to use advanced features.
Simple search is handy. We just need to include resolved reports too. :)
Darrell
6:56 a.m.
On 04/17/2012 12:36 AM, Timothy Pearson wrote:
Yes we can. It's a good idea and I need to figure out how to set it up.
If you don't see progress please remind me via Email--things are hectic
here but I would like to get this feature in place.
Tim
Ok!
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.
Tim,
A long while back we added a empty email address to every single bug
report, one that automagically is on the email list of all new bugs as
well. I think the idea was that this email account would forward to some
sort of list that people could subscribe to and receive bug reports from
all bugs. Obviously that would only be a few developers who are
sufficiently interested.
What say you? Can we do this?
Calvin 
16 Apr
16 Apr
6:01 p.m.
New subject: [trinity-devel] Bug tracker update
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?
http://bugs.pearsoncomputing.net/bugzilla/bugzilla/bugzilla/buglist.cgi?qui
cksearch=%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/buglis
t.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
Good job, Darell.
Bug
http://bugs.pearsoncomputing.net/bugzilla/bugzilla/bugzilla/show_bug.cgi?id…
has "build issue" in the text, but not in the subject. Is this correct?
Slávek
--
6:58 p.m.
New subject: [trinity-devel] Bug tracker update
Bug
http://bugs.pearsoncomputing.net/bugzilla/bugzilla/bugzilla/show_bug.cgi?id…
has "build issue" in the text, but not in the subject. Is this correct?
Yes. I noticed that too. I don't know whether I can edit a previous comment entry (I
wrote the text), but even if I could, the comment suggests the problem might be a build
issue.
Here is an updated search string that ignores body text:
http://bugs.pearsoncomputing.net/bugzilla/bugzilla/bugzilla/bugzilla/buglis…
The result is 71 reports.
Darrell
4415
days inactive
4416
days old
8 comments
4 participants
participants (4)
-
Calvin Morrison -
Darrell Anderson -
Slávek Banko -
Timothy Pearson