of a group per project, and automatically put new bugs against that
project into that group, thus allowing entire projects to be protected
against viewing by unauthorized users. This is all optional,
controlled by new parameters.
"editbugs" and "canconfirm". People without these states are now much
more limited in what they can do.
For backwards compatability, by default all users will have the
editbugs and canconfirm bits on them. Installing this changes as is
should only have one major visible effect -- an UNCONFIRMED state
will appear in the query page. But no bugs will become in that state,
until you tweak some of the new voting-related parameters you'll find
when editing products.
me. Added a footer to every page. Add some options to do things like
display checkboxes instead of scrolling lists, and a new formatting
for email diffs, and show list items capitalized instead of all upper
case.
add to beginning of bug entry form. also aligned text in the form
to make it pretty. Uncomment the <!--</tr><tr>--> if people complain
the 80 col description text box doesn't fit narrow screens.
on the the login name that will be used as the "reporter" (to more
completely represent the bug report, and to prevent people from forgetting
to switch logins when using another person's browser).
now choose whether to let submitters of new bugs choose a priority, or whether
they should just accept the default priority (which is now no longer hardcoded
to "P2", but is instead a param.) The default value of the params will cause
the same behavior as before.
don't let people file new bugs against this product. (This is for when a
product is retired, but you want to keep the bug reports around for posterity.)
donm%bluemartini.com
endico%mozilla.org
terry%mozilla.org
dmose%mozilla.org
bryce-mozilla%nextbus.com
terry%netscape.com