Very close to finishing Bugzilla 2.20. Opinions wanted.

[Olav Vitters]

[ Initially mailed to bugmaster@.... I want your comments too. ]

http://bugzilla-test.gnome.org/ is almost the way I want it to be.
There are only a few items on the TODO list:
 * Fix sanitycheck errors on bugzilla.gnome.org
 * Add classifications to simple-bug-guide.cgi
 * Further enhance show_bug.cgi:
   * When lacking permissions, add bugsquad promotion message
     (this is partly done.. together with needinfo & wontfix
     explanations)
   * When logged off, add login box that should reload the page and stay
     on the same bug
   * When status whiteboard begins with a capital and ends with a '.',
     show that message at the top of the bugreport.
 * Cleanup http://bugzilla-test.gnome.org/page.cgi?id=reports.html
   * Move some of the stuff to browse.cgi and just mention browse.cgi or
     describeuser.cgi (which again links to browse.cgi)
   * Add the 2.18 and 2.20 specific reports (charting and such)
 * TEST TEST TEST! (ask bugsquad to help?)
 * Ask desktop-devel-list for opinions? hmm.. might not want to ;)

Also a few reports still need to be ported over (gnome-report.cgi). Some
reports will not be ported. Status of this is on
http://live.gnome.org/BugzillaUpgrade/UpgradeStatus. Usually a report
will not be ported if it wasn't working on 2.16.

Oh just saw that we need to wait for Boogle also :)

Before I ask the bugsquad to look at this I want your opinions. I plan
to divide any remarks (yours, bugsquad, d-d-l?) into stuff that must be
fixed before b.g.o switches over and stuff that can be fixed after that.
Bugzilla-test seems to forget bugmasters can do everything, so just give
yourself admin privileges.

I'd want to upgrade b.g.o on Sunday 18 December. Monday 12 December is
the latest that I want to announce the downtime. If there are still big
things to be fixed on that Monday, I'll delay with a week (and keep
delaying until all is ok).

http://live.gnome.org/BugzillaUpgrade/UpgradeStatus lists some of the
niceties of bugzilla-test, but it is far more than on that page.

--
Regards,
Olav
_______________________________________________
bugzilla-devel-list mailing list
bugzilla-devel-list@...
http://mail.gnome.org/mailman/listinfo/bugzilla-devel-list

[Thierry Moisan]

Olav Vitters a écrit :

>[ Initially mailed to bugmaster@.... I want your comments too. ]
>
>http://bugzilla-test.gnome.org/ is almost the way I want it to be.
>There are only a few items on the TODO list:
>
> * TEST TEST TEST! (ask bugsquad to help?)
>  
>
Hi, I tested a bit bugzilla 2.20 and I found some strange things :

1. I think that when changing something in a bug, the "Bug Reassignment"
options (at the end of the bug page) default option shouldn't be "
Reassign bug to default assignee and QA contact of selected component"
but "Leave assigned to xxxxxx" . I think that when we do a change like
just a comment and setting as new or something else, we don't want to
change anything else. But if someone else than the default assignee
(wich I think is the component owner right?) as this bug assigned to
him, there could be so mix up.

2. bugzilla 2.20 doesn't allow any reopen status after needinfo status
as been set...

Good work!

Thierry Moisan
_______________________________________________
bugzilla-devel-list mailing list
bugzilla-devel-list@...
http://mail.gnome.org/mailman/listinfo/bugzilla-devel-list

[Olav Vitters]

On Mon, Nov 28, 2005 at 05:43:19PM +0100, Olav Vitters wrote:
> [ Initially mailed to bugmaster@.... I want your comments too. ]

PS: Mail has been disabled. Feel free to change bugs as you want. I'll
announce when it will be enabled again (probably only a few days before
we upgrade).

--
Regards,
Olav
_______________________________________________
bugzilla-devel-list mailing list
bugzilla-devel-list@...
http://mail.gnome.org/mailman/listinfo/bugzilla-devel-list

[Olav Vitters]

On Mon, Nov 28, 2005 at 01:04:30PM -0500, Thierry Moisan wrote:

> Olav Vitters a écrit :
>
> >[ Initially mailed to bugmaster@.... I want your comments too. ]
> >
> >http://bugzilla-test.gnome.org/ is almost the way I want it to be.
> >There are only a few items on the TODO list:
> >
> >* TEST TEST TEST! (ask bugsquad to help?)
> >
> >
> Hi, I tested a bit bugzilla 2.20 and I found some strange things :
>
> 1. I think that when changing something in a bug, the "Bug Reassignment"
> options (at the end of the bug page) default option shouldn't be "
> Reassign bug to default assignee and QA contact of selected component"
> but "Leave assigned to xxxxxx" . I think that when we do a change like
> just a comment and setting as new or something else, we don't want to
> change anything else. But if someone else than the default assignee
> (wich I think is the component owner right?) as this bug assigned to
> him, there could be so mix up.

Default assignee is the component owner indeed (usually the
product-maint@....

The show_bug page will not actually select 'Reassign bug to default
assignee and QA contact of selected component' by default. When loading
the page it will check if the current owner is the default
assignee/owner. If that is the case this option will be enabled.

When the current owner/assignee is *not* the default one, the 'leave
assigned to xxx' will be selected.

Above is intended to easily allow someone to move bugs between products.
When a bug was assigned to a specific person, the bug will still be
assigned to that person. When a bug was not specifically assigned,
moving to another product should reassign to the owner of the new
product.

In a ASCII art table to make more clear:

                     | Is assigned to    | Is NOT assigned to |
                     | the default owner | the default owner  |
---------------------------------------------------------------
Will be reassigned   | YES               | NO                 |
on product change    |                   |                    |
---------------------------------------------------------------
Leave assigned to    | NO                | YES                |
xxx is selected      |                   |                    |
---------------------------------------------------------------
Reassign to def.owner| YES               | NO                 |
+QA is selected      |                   |                    |
---------------------------------------------------------------

If above table doesn't make sense, just reassign a bug to yourself and
visit the bug again. Then reassign the bug again to the default owner
and revisit the bug. Make sure to actually visit the bug again (and not
reload it in another tab), cause Mozilla remembers the selected form
options.


Also different from a normal Bugzilla, reassignments will *not* change
the status of a bug to NEW! This is on purpose.

> 2. bugzilla 2.20 doesn't allow any reopen status after needinfo status
> as been set...

Whoops. Added the reopen back. Have to check for further forgotten
status changes. Possibly forgotten others as well.

--
Regards,
Olav
_______________________________________________
bugzilla-devel-list mailing list
bugzilla-devel-list@...
http://mail.gnome.org/mailman/listinfo/bugzilla-devel-list