bug queries can be run against it, so that these slow queries won't be
able to tie up the rest of the system.
git-svn-id: svn://10.0.0.236/trunk@61227 18797224-902f-48f8-a5cc-f745e15eee43
"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.
git-svn-id: svn://10.0.0.236/trunk@61184 18797224-902f-48f8-a5cc-f745e15eee43
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.
git-svn-id: svn://10.0.0.236/trunk@58576 18797224-902f-48f8-a5cc-f745e15eee43
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.)
git-svn-id: svn://10.0.0.236/trunk@58443 18797224-902f-48f8-a5cc-f745e15eee43
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.
git-svn-id: svn://10.0.0.236/trunk@58426 18797224-902f-48f8-a5cc-f745e15eee43
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...
git-svn-id: svn://10.0.0.236/trunk@58412 18797224-902f-48f8-a5cc-f745e15eee43
option to skip the database check (since that code doesn't work with
all versions of MySQL/Msql-mysql/Perl/moonphase).
git-svn-id: svn://10.0.0.236/trunk@58401 18797224-902f-48f8-a5cc-f745e15eee43
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.
git-svn-id: svn://10.0.0.236/trunk@58386 18797224-902f-48f8-a5cc-f745e15eee43
table. There is now a separate entry for each new long description,
rather than appending them all together in one big field.
git-svn-id: svn://10.0.0.236/trunk@58319 18797224-902f-48f8-a5cc-f745e15eee43
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.
git-svn-id: svn://10.0.0.236/trunk@58008 18797224-902f-48f8-a5cc-f745e15eee43
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".
git-svn-id: svn://10.0.0.236/trunk@56992 18797224-902f-48f8-a5cc-f745e15eee43
user in the profiles table, then this user will be promoted into all groups.
git-svn-id: svn://10.0.0.236/trunk@50473 18797224-902f-48f8-a5cc-f745e15eee43
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!
git-svn-id: svn://10.0.0.236/trunk@50467 18797224-902f-48f8-a5cc-f745e15eee43
