Re: Done: Planned changes to bugzilla step 2

Hi Hb

Hb wrote:

> Perhaps another change to bugzilla was unnoticed.  The predefined search "My
> Bugs" now encloses all bugs where the user is QA Contact too.

This is noted already, thanks.

However, this is only one aspect. As per my post in the forums, the main
problem for me is that the bug is by default, not assigned to me as the
module maintainer.

I may not be able to get to my email to even notice for some hours, or
more. And then i have to actually go to the website and assign the bug
to myself which sounds trivial, but not when you have a number of bugs,
or even emails you need to address daily (from xaraya or other places).

In some cases, one just plainly misses the notification the first time
through the mail box.

My request is similar to requests made years ago for maintainers at that
time - that the bug be automatically assigned by default to the module
maintainer.

Assigning the bug by default to the module maintainer, prevents a lot of
hassle in many ways, as per the details in the post on the forums on the
bugzilla and QA topic.

Would have been good if this was posted there, as this now breaks the
flow of discussion on this topic there, and either means a double post
back or info is 'missing' in the forum topic.

Post on the forum is by request of Chris who had the same request as me
re the default assigment for a bug.

http://xaraya.com/index.php/xarbb/topic/3343

> 
> Are those reminders so valuable to step back to the old method?  To a method
> that let to ~1,000 bugs which were *formally assigned* over several years but no
> resolution was given?

Whether those bugs were assigned or not really makes no diference.
If people wanted a bug fixed, or had a patch, or wanted to fix it
directly (if they were a committer), then it was discussed and they did
fix it.


The fact that there is or was 1,000 bugs which were formally assigned
but no resoluation is due to a number of factors.

1. No one wanted to fix it of the committers

2. No patches were received from anyone that might have wanted to fix it

3. The main one: Many bugs were marked as 'later', remind, or 'after
1.0' by either the module maintainer or by the bugzilla maintainer
(miko), or the release mananager (or similar depending at the time).
This was the majority. After 1.0 xaraya was released, all these bugs,
going way back from 2003 to 2006 was changed automatically to OPEN.

If patches were submitted after this time of reopening - then if it
wasn't fixed or attended to, it was highly likely due to the lack of
activity more generally in the project, than anything to do with the
initial assignment of the bug.

If someone wants to publicize the process even further, that anyone can
submit patches to any bug (most people would know this I think), then it
would improve it. There is a document that was regularly publicized and
made featured article or other mechanism, about submitting patches too
in the past. The patch submission document is still there.

Jo




-- 
http://xarigami.com :: Creative web development with Xaraya
http://2skies.com   :: Open source hosting and development