add a stack to save the current global SQL state so that queries can be nested.  used this mechanism to fix the 62618 regression.  r=encido@mozilla.org

patch from Jake <jsteenhagen@novagate.com> to fix bug 59515; adds a title attribute containing status and short description to various bug links.  In some browsers (most Mozilla builds, at least) this makes the status and short description available as a tooltip, so it is no longer necessary to click through to see it. r=dmose@mozilla.org

patch by jmrobin@tgix.com

patch submitted by john.beranek@pace.co.uk (John Beranek)

change '@::legal_resolution_no_dup' to '@::settable_resolutions'. This a list of  resolutions which a bug may be changed to in the bug form and consists of all legal resolutions except 'MOVED' and 'DUPLICATE', since setting a bug to those resolutions requires a special process.

Keywords were already enforced to never differ only in capitalization.  So, changed the code so that case no longer matters when typing in the name of a keyword.

sstock@iconnect-inc.com, reworked slightly by cyeh@bluemartini.com
to update it to the tip

calls from bug_form.

entered in that information. Thanks to
Chris Baldwin <cbaldwin@redback.com>
for providing the patch.

of different target milestones by product.

busting other people trying to use the system.

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

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.

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.

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

connection info.

bottom.  Made "My bugs" show bugs you own AND bugs you submitted.
Added ability to display your named queries in the footer.  Many
random bugfixes.

Added "My votes" link to footer.  Other minor voting-related fixes.

the database, rather than in cookies.  This means you have to log
in to use these features, but I have plans that require them to be
server-side.  (Besides, some people were beginning to run out of
cookie space.)

dependent bugs.

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.