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.

confidentiality when submitting a new bug.

string wasn't working with modern MySQL engines.

bug_email.pl script.  See comments in the script itself for how it works.

more useragent strings.

bug-writing guidelines.

have a universal (and more noticable) way of displaying them.

for which project to use.

to the shadow database.

Wasn't always tweaking LOCK TABLES commands correctly when shadowing.  And finally fixed it to actually generate useful SQL error messages.

bug queries can be run against it, so that these slow queries won't be
able to tie up the rest of the system.

were changing the resolution, even if they weren't.

of places.

logged in.  Since they haven't logged in, we don't know what they will
be allowed to do.  And users who disable cookies tend to pretty often
not be logged in.

the permissions of other users.

someone changed something.

"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.

Lock the tables as low-priority when writing.  Maybe makes people making changes wait longer, but people doing read-only stuff should now never block for very long.

Patches by Ken Jenks <kjenks@abiblion.com> and jug@tellux.de -- make the Javascript behave under IE5 and under Netscape 3.x

Patches by Ken Jenks <kjenks@abiblion.com> and jug@tellux.de -- make the Javascript behave under IE5 and under Netscape 3.x