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

This implements canonical email address transformation.  i.e., you have the option of setting up bug_email.pl to search the profiles database for a username which has the same username (before the @) same username and base domain (seth@cs.brandeis.edu = seth@job.cs.brandeis.edu) or identical email address (old behavior) based on the From email address.  See the code for a more sensical description.

o this is a minor step towards getting canonical email addresses to work, and not via a gross hack (the script with a gross hack is in use in a production environment, so ...)

Anyways, this address the findUser() sub and email transforms of none, base domain, and name only.  base_domain is not properly implemented yet.  an email transform of none does an exact match on email addresses in the profiles table.  A name only transform does a regular expression match (via mysql's RLIKE operator) on the name portion of the address (i.e., seth from seth@job.cs.brandeis.edu).  This is sloppy, but useful in an environment where there are only a few users.

the base_domain is next, probably tomorrow.  I need to figure out how to implement it first.

this is the initial checkin of the bug_email.pl script into the bugzilla cvs tree under the contrib directory.  This is not my code, but I'm championing its maintanence right now, since I'm using and hacking on it heavily.  The list of contributors can be found in the file itself.

Changes I've made :
- updated to the newest CVS pull of bugzilla
- works out of contrib/bugzilla
- put in the MPL license header

Directions for use are in the file itself.  Essentially, you put in a procmailrc entry which cats the message to this script.

Changes coming in the near future ...

- canonical email transformation (i.e., seth@job.cs.brandeis.edu == seth@cs.brandeis.edu)
- default product and component (i.e., if you don't specify a product and component, it goes into a PENDING product)
- querying a bug over email
- appending a bug over email
- keywords over email
- use the globals.pl parameters functionality to edit and save this script's parameters
- integrate some setup in the checksetup.pl script

FWIW, the first two things are necessary for this to be useful in my setup, so they get an overwhelming bit of priority

"check all" and "uncheck all" buttons work on IE.

name of the query had a space in it.

is uglier, but often squeezes things better horizontally.

correctly.

bug was actually a legal bug number.

should have always had this behavior.