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.)
unique. Sure enough, somehow, I got 22 duplicated entries in my
database. This code detects that, cleans up the duplicates, and then
tweaks the table to declare the field to be unique. What a pain.
it got run more than once. This checkin fixes that, and also changes
the DumpBugActivity() routine to give me enough information to
hopefully repair the damaged mozilla.org database...
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.
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.
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".
yicky old make*.sh files and the CHANGES file with a new, nifty
checksetup.pl file that knows how to create a setup from scratch as
well as upgrade an older setup to a new one. Very cool stuff!
terry%mozilla.org
dmose%mozilla.org