of different target milestones by product.

midair collision happens which needs to generate text which needs to
look at the attachments table.  Sigh.

the difference between new comments and people copying stuff in from
old comments.

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

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.

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.

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.

bug was actually a legal bug number.

should have always had this behavior.

different fields we keep an activity log on.  The bugs_activity table
now has a pointer into that table instead of recording the name directly.

Set up a new, highly experimental email-notification scheme.  To turn
it on, the maintainer has to turn on the "New email tech" param, and
then individual users have to turn on the "New email tech" preference.

table.  There is now a separate entry for each new long description,
rather than appending them all together in one big field.

of all the keywords assigned to the bug.  Right now, we only have code
that generates and maintains this field; soon will come code that
actually uses it.

reassigning by component, reassign the qa contact too.

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.

away from them or they get removed from the CC list.

changing keywords.

field.  This caused mid-air collisions and other weirdnesses.

authority maintain a list of keywords, and users can associate any
keyword with any bug.

The new functionality won't appear until at least one keyword is
defined.

Note that you *must* run the "checksetup.pl" script after updating
this change, in order to create the new required tables "keywords" and
"keyworddefs".

Patch by freitag@suse.de (Klaas Freitag) -- add options to let Bugzilla require comments on certain operations.

reassign-to-component-owner.

be fixed.

Patch by holger@holger.om.org (Holger Schurig) -- put the fancy header on several pages that were missing it.

use "when" as a column name, so let's change our usage while it's
still easy to do so.

other ones.

py8ieh=bugzilla@bath.ac.uk).

the change (after all, they are right there viewing things interactively).
To make this clear to everyone, print out the exact email list as each
bug is processed.