Hacking Bugzilla

Chapter 4. Administering Bugzilla
Or, I just got this cool thing installed. Now what the heck do I + do with it? +
So you followed "

You may find this example illustrative for how bug groups work. +
Example 4-7. Bugzilla Groups
Bugzilla Groups example
+-----------------------
+
+For this example, let us suppose we have four groups, call them
+Group1, Group2, Group3, and Group4.
+
+We have 5 users, User1, User2, User3, User4, User5.
+
+We have 8 bugs, Bug1, ..., Bug8.
+
+Group membership is defined by this chart:
+(X denotes that user is in that group.)
+(I apologize for the nasty formatting of this table.  Try viewing
+it in a text-based browser or something for now. -MPB)
+
+      G G G G
+      r r r r
+      o o o o
+      u u u u
+      p p p p
+      1 2 3 4
+     +-+-+-+-+
+User1|X| | | |
+     +-+-+-+-+
+User2| |X| | |
+     +-+-+-+-+
+User3|X| |X| |
+     +-+-+-+-+
+User4|X|X|X| |
+     +-+-+-+-+
+User5| | | | |
+     +-+-+-+-+
+
+Bug restrictions are defined by this chart:
+(X denotes that bug is restricted to that group.)
+
+     G G G G
+     r r r r
+     o o o o
+     u u u u
+     p p p p
+     1 2 3 4
+    +-+-+-+-+
+Bug1| | | | |
+    +-+-+-+-+
+Bug2| |X| | |
+    +-+-+-+-+
+Bug3| | |X| |
+    +-+-+-+-+
+Bug4| | | |X|
+    +-+-+-+-+
+Bug5|X|X| | |
+    +-+-+-+-+
+Bug6|X| |X| |
+    +-+-+-+-+
+Bug7|X|X|X| |
+    +-+-+-+-+
+Bug8|X|X|X|X|
+    +-+-+-+-+
+
+Who can see each bug?
+
+Bug1 has no group restrictions.  Therefore, Bug1 can be seen by any
+user, whatever their group membership.  This is going to be the only
+bug that User5 can see, because User5 isn't in any groups.
+
+Bug2 can be seen by anyone in Group2, that is User2 and User4.
+
+Bug3 can be seen by anyone in Group3, that is User3 and User4.
+
+Bug4 can be seen by anyone in Group4.  Nobody is in Group4, so none of
+these users can see Bug4.
+
+Bug5 can be seen by anyone who is in _both_ Group1 and Group2.  This
+is only User4.  User1 cannot see it because he is not in Group2, and
+User2 cannot see it because she is not in Group1.
+
+Bug6 can be seen by anyone who is in both Group1 and Group3.  This
+would include User3 and User4.  Similar to Bug5, User1 cannot see Bug6
+because he is not in Group3.
+
+Bug7 can be seen by anyone who is in Group1, Group2, and Group3.  This
+is only User4.  All of the others are missing at least one of those
+group priveleges, and thus cannot see the bug.
+
+Bug8 can be seen by anyone who is in Group1, Group2, Group3, and
+Group4.  There is nobody in all four of these groups, so nobody can
+see Bug8.  It doesn't matter that User4 is in Group1, Group2, and
+Group3, since he isn't in Group4.
+
+
There is also a project, based upon somewhat dated Bugzilla + code, to integrate CVS and Bugzilla through CVS' ability to + email. Check it out at: + http://homepages.kcbbs.gen.nz/~tonyg/, under the + "cvszilla" link. +
The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do - not have more information about it right now, and most of what - went into the "future" section is now present. That stuff was - blue-sky a year ago; MattyT should have me a new document - sometime... +> Bugzilla's future is a constantly-changing thing, as various developers + "scratch an itch" when it comes to functionality. + Thus this section is very malleable, subject to change without notice, etc. + You'll probably also notice the lack of formatting. I apologize that it's + not quite as readable as the rest of the Guide. +

                               Bugzilla Blue Sky
+
+Customisability
+
+   One of the major stumbling blocks of Bugzilla has been that it is too
+   rigid and does not adapt itself well enough to the needs of an
+   organisation.  This has led to organisations making changes to the
+   Bugzilla code that need to be redone each new version of Bugzilla.
+   Bugzilla should attempt to move away from this to a world where this
+   doesn't need to occur.
+
+   Most of the subsections in this section are currently explicit design
+   goals for the "Bugzilla 3" rewrite.  This does not necessarily mean
+   that they will not occur before them in Bugzilla 2, but most are
+   significant undertakings.
+
+  Field Customisation
+
+   Many installations wish to customise the fields that appear on bug
+   reports.   Current versions of Bugzilla offer limited
+   customisability.  In particular, some fields can be turned off.
+
+   However, many administrators wish to add their own fields, and rename
+   or otherwise modify existing fields.  An architecture that supports
+   this would be extraordinarily useful.
+
+   Indeed, many fields work similarly and could be abstracted into "field
+   types", so that an administrator need write little or no code to
+   support the new fields they desire.
+
+   Possible field types include text (eg status whiteboard), numbers,
+   dates (eg report time), accounts (eg reporter, qa, cc), inter-bug
+   relationships (dependencies, duplicates), option groups (platform, os,
+   severity, priority, target milestone, version) etc.
+
+   Ideally an administrator could configure their fields through a
+   Bugzilla interface that requires no code to be added.  However, it is
+   highly unlikely this ideal will never be met, and in a similar way
+   that office applications have scripting languages, Bugzilla should
+   allow new field types to be written.
+
+   Similarly, a common desire is for resolutions to be added or removed.
+
+    Allocations
+
+   ?
+
+    Option Groups
+
+   ?
+
+    Relations
+
+   ?
+
+  Database Integrity
+
+   Furthermore, it is desirable for administrators to be able to specify
+   rules that must or should apply between the fields on a bug report.
+
+   For example, you might wish to specify that a bug with status ASSIGNED
+   must have a target milestone field that that is not untargetted.  Or
+   that a bug with a certain number of votes should get ASSIGNED.  Or
+   that the QA contact must be different from the assignee.
+
+   "Must" relationships could be implemented by refusing to make changes
+   that violate the relationships, or alternatively, automatically
+   updating certain fields in order to satisfy the criteria.  Which
+   occurs should be up to the administrator.
+
+   "Should" relationships could be implemented by a combination of
+   emitting warnings on the process bug page, the same on notification
+   mails, or emitting periodic whine mails about the situation.  Again,
+   which occurs should be up to the administrator.
+
+   It should also be possible for whine mails to be emitted for "must"
+   relationships, as they might become violated through direct database
+   access, Bugzilla bugs, or because they were there before the
+   relationship was enforced.
+
+   As well as implementing intra-bug constraints, it would be useful to
+   create inter-bug constraints.  For example, a bug that is dependent on
+   another bug should not have an earlier milestone or greater priority
+   than that bug.
+
+  Database Adaptability
+
+   Often an administrator desires that fields adapt to the values of
+   other fields.  For example, the value of a field might determine the
+   possible values of another field or even whether it appears (whether
+   it is "applicable").
+
+   Limited adaptability is present in Bugzilla 2, and only on the
+   "Product" field:
+     * The possible values of the target milestone, version and component
+       fields depend on the product.
+     * UNCONFIRMED can be turned off for specific products.
+     * Voting can be configured differently or turned off for different
+       products, and there is a separate user vote limits for each
+       product.
+
+   It would be good if more adaptability was present, both in terms of
+   all fields relying on the product, as well as the ability to adapt
+   based on the value of all fields.
+
+   Example ???
+
+   General adaptability raises the issue of circular references between
+   fields causing problems.  One possible solution to this is to place
+   the fields in a total ordering and require a field refer only to the
+   previous fields.
+
+   In Bugzilla 2, changing the product of a bug meant a second page would
+   appear that allowed you to choose a new milestone, component and
+   version, as those fields adapted themselves to the new product.  This
+   page could be generalised to support all instances where:
+     * a field value must or might be changed because the possible values
+       have changed
+     * is going to drop off because it it is no longer applicable, and
+       this should be confirmed
+     * must be specified because it is suddenly applicable, and the
+       default value, if one exists, might not be acceptable
+
+  Database Independence
+
+   Currently Bugzilla only runs on the MySQL database.  It would be
+   desirable for Bugzilla to run on other databases, because:
+     * Organisations may have existing database products they use and
+       would prefer to run a homogenous environment.
+     * Databases each have their own shortcomings, including MySQL.  An
+       administrator might choose a database that would work better with
+       their Bugzilla.
+
+   This raises the possibility that we could use features that are only
+   present in some databases, by appropriately falling back.  For
+   example, in the MySQL world, we live without:
+     * record-level locking, instead we use table-level locking
+     * referential and record constraints, instead we checking code
+     * subselects, instead we use multiple queries and redundant "caches"
+
+  Multiple Front Ends
+
+   Currently Bugzilla is manipulated via the Web, and notifies via
+   E-Mail.  It would be desirable for Bugzilla to easily support various
+   front ends.
+
+   There is no reason that Bugzilla could not be controlled via a whole
+   range of front ends, including Web, E-Mail, IRC, ICQ, etc, and
+   similarly for how it notifies.  It's also possible that we could
+   introduce a special Bugzilla client that uses its own protocol, for
+   maximum user productivity.
+
+   Indeed a request reply might be returned via a totally different
+   transport method than was use to submit the request.
+
+Internationalisation
+
+   Bugzilla currently supports only English.  All of the field names,
+   user instructions, etc are written in English.  It would be desirable
+   to allow "language packs" so Bugzilla can be easily used in
+   non-English speaking locales.
+
+   To a degree field customisation supports this, because administrators
+   could specify their own fields names anyway.  However, there will
+   always be some basic facilities not covered by this, and it is
+   desirable that the administrator's interface also is
+   internationalisable.
+
+Better Searching
+
+  General Summary Reports
+
+   Sometimes, the normal querying page leaves a lot to be desired.  There
+   are other facilities already in place or which people have asked for:
+
+   Most Doomed Reports - All Bugs or All Bugs In A Product, Categorised
+   On Assignee, Shows and Counts Number of Bugs For Each Assignee
+   Most Voted For Bugs - All Bugs, Categorised On Product, Shows Top Ten
+   Bugs Voters Most Want Fixed
+   Number of Open Bugs For An Assignee - Bug List, Categorised On
+   Developers, Counts Number of Bugs In Category
+
+   The important thing to realise is that people want categorised reports
+   on all sorts of things - a general summary report.
+
+   In a categorised report, you choose the subset of bugs you wish to
+   operate on (similar to how you would specify a query), and then
+   categorise them on one or more fields.
+
+   For each category you display the count of the number of things in
+   that category.  You can optionally display the bugs themselves, or
+   leave them out, just showing the counts.  And you can optionally limit
+   the number of things (bugs or subcategories) that display in each
+   category.
+
+   Such a mechanism would let you do all of the above and more.
+   Applications of this mechanism would only be recognised once it was
+   implemented.
+
+  Related Bugs
+
+   It would be nice to have a field where you could enter other bugs
+   related to the current bug.  It would be handy for navigation and
+   possibly even finding duplicates.
+
+  Column Specification Support
+
+   Currently bug lists use the columns that you last used.  This doesn't
+   work well for "prepackaged queries", where you followed a link.  You
+   can probably add a column by specifying a sort column, but this is
+   difficult and suboptimal.
+
+   Furthermore, I find that when I want to add a column to a bug list,
+   it's usually a one off and I would prefer it to go away for the next
+   query.  Hence, it would be nice to specify the columns that appear on
+   the bug list (and general summary report) pages.  The default query
+   mechanism should be able to let you specify your default columns.
+
+  Advanced Querying Redesign
+
+   ?
+
+Keywords
+
+   People have a need to apply tags to bugs.  In the beginning, people
+   placed designators in the summary and status whiteboard.  However,
+   these fields were not designed for that, and so there were many flaws
+   with this system:
+     * They pollute the field with information that was never intended to
+       be present.
+     * Removing them with a bulk change is a difficult problem that has
+       too many pitfalls to implement.
+     * You can easily get the capitalisation wrong.
+
+   Then dependencies were introduced (when?), and people realised that
+   they could use them for "tracking bugs".  Again, dependencies were not
+   designed for that, and so there were more flaws, albeit different
+   ones, including:
+     * They aren't really bugs, so it's difficult to distinguish issues
+       from bugs.
+     * They can pollute bugs counts, and you must somehow exclude them
+       from queries.
+     * There is a whole lot of useless information on them.  They have an
+       assignee but there is nothing to fix, and that person can get
+       whined at by Bugzilla.  They have target milestones which must be
+       manually maintained.  And so on.
+
+   Finally, keywords were introduced (when?) for this purpose to remove
+   the need for these two systems.  Unfortunately, the simple keywords
+   implementation was itself lacking in certain features provided by the
+   two previous systems, and has remained almost unchanged since its
+   inception.  Furthermore, it could not be forseen that in large
+   installations, the sheer number of keywords could become unwieldly and
+   could lead to a movement back to the other systems.
+
+   The keywords system was the right idea, however, and it remains so.
+   Fixing the keywords system is one of the most important Bugzilla
+   issues.
+
+  Bringing Keywords Up To Par
+
+   For the most part, keywords are very good at what they do.  It is easy
+   to add and remove them (unlike summary/whiteboard designators), we can
+   simply see what issues are present on a bug (unlike tracking bugs),
+   and we do not confuse bugs with issues (unlike tracking bugs).
+
+   However, there are still some "regressions" in the keyword system over
+   previous systems:
+     * Users wish to view the "dependency forest" of a keyword.  While a
+       dependency tree is of one bug, a dependency forest is of a bug
+       list, and consists of a dependency tree for each member of the bug
+       list.  Users can work around this with tracking bugs by creating a
+       tracking bug and viewing the dependency tree of that tracking bug.
+     * Users wish to specify the keywords that initially apply to a bug,
+       but instead they must edit the bug once it has already been
+       submitted.  They can work around this with summary designators,
+       since they specify the summary at reporting time.
+     * Users wish to store or share a bug list that contains a keywords
+       column.  Hence they wish to be able to specify what columns appear
+       in the bug list URL, as mentioned earlier.  They can work around
+       this using summary designators, since almost all bug lists have a
+       summary column.
+     * Users wish to be able to view keywords on a bug list.  However
+       often they are only interested in a small number of keywords.
+       Having a bug list with a keywords column means that all keywords
+       will appear on a bug list.  This can take a substantial amount of
+       space where a bug has a lot of keywords, since the table columns
+       in Bugzilla adjust to the largest cell in that column.  Hence
+       users wish to be able to specify which keywords should appear in
+       the bug list.  In a very real sense, each keyword is a field unto
+       itself.  Users can work around this by using summary designators,
+       since they keywords will share the space in the summary column.
+     * Users wish to know when bugs with a specific issue are resolved.
+       Hence they wish to be able to receive notifications on all the
+       bugs with a specific keyword.  The introduction a generic watching
+       facility (also for things like watching all bugs in a component)
+       would achieve this.  Users can work around this by using tracking
+       bugs, as dependencies have an existing way of detecting fixes to
+       bug a bug was blocked by.
+
+  Dealing With The Keyword Overload
+
+   At the time of writing, the mozilla.org installation has approximately
+   100 keywords, and many more would be in use if the keywords system
+   didn't have the problems it does.
+
+   Such a large number of keywords introduces logistical problems:
+     * It must be easy for someone to learn what a keyword means.  If a
+       keyword is buried within a lot of other keywords, it can be
+       difficult to find.
+     * It must be easy to see what keywords are on a bug.  If the number
+       of keywords is large, then this can be difficult.
+
+   These lead some people to feel that there are "too many keywords".
+
+   These problems are not without solutions however.  It is harder to
+   find a list of designators or tracking bugs than it is a list of
+   keywords.
+
+   The essential problem is it needs to be easy to find the keywords
+   we're interested in through the mass of keywords.
+
+    Keyword Applicability
+
+   As has been previously mentioned, it is desirable for fields to be
+   able to adapt to the values of other fields.  This is certainly true
+   for keywords.  Many keywords are simply not relevant because of the
+   bugs product, component, etc.
+
+   Hence, by introducing keyword applicability, and not displaying
+   keywords that are not relevant to the current bug, or clearly
+   separating them, we can make the keyword overload problem less
+   significant.
+
+   Currently when you click on "keywords" on a bug, you get a list of all
+   bugs.  It would be desirable to introduce a list of keywords tailored
+   to a specific bug, that reports, in order:
+     * the keywords currently on the bug
+     * the keywords not currently on the bug, but applicable to the bug
+     * optionally, the keywords not applicable to the bug
+
+   This essentially orders the keywords into three groups, where each
+   group is more important than the previous, and therefore appears
+   closer to the top.
+
+    Keyword Grouping & Ordering
+
+   We could further enhance both the global and bug specific keyword list
+   by grouping keywords.  We should always have a "flat" view of
+   keywords, but other ways of viewing the keywords would be useful too.
+
+   If keyword applicability was implemented, we could group keywords
+   based on their "applicability condition".  Keywords that apply to all
+   bugs could be separated from keywords that apply to a specific
+   product, both on the global keyword list and the keyword list of a bug
+   that is in that product.
+
+   We could specify groups of our own.  For example, many keywords are in
+   a mutually exclusive group, essentially like radio buttons in a user
+   interface.  This creates a natural grouping, although other groupings
+   occur (which depends on your keywords).
+
+   It is possible that we could use collapsing/expanding operations on
+   "twisties" to only should the groups we are interested in.
+
+   And instead of grouping keywords, we could order them on some metric
+   of usefulness, such as:
+     * when the keyword was last added to a bug
+     * how many bugs the keyword is on
+     * how many open bugs the keyword is on
+
+    Opting Out Of Keywords
+
+   Not all people are going to care about all keywords.  Therefore it
+   makes sense that you may wish to specify which keywords you are
+   interested in, either on the bug page, or on notifications.
+
+   Other keywords will therefore not bother users who are not interested
+   in them.
+
+  Keyword Security
+
+   Currently all keywords are available and editable to all people with
+   edit bugs access.  This situation is clearly suboptimal.
+
+   Although relying on good behaviour for people to not do what they
+   shouldn't works reasonably well on the mozilla.org, it is better to
+   enforce that behaviour - it can be breached through malice, accident
+   or ignorance.
+
+   And in the situation where it is desirable for the presence or absence
+   of a keyword not to be revealed, organisations either need to be
+   content with the divulgence, or not use keywords at all.
+
+   In the situation where they choose to divulge, introducing the ability
+   to restrict who can see the keyword would also reduce keyword
+   overload.
+
+  Personal Keywords
+
+   Keywords join together a set of bugs which would otherwise be
+   unrelated in the bug system.
+
+   We allow users to store their own queries.  However we don't allow
+   them to store their own keywords on a bug.  This reduces the
+   usefulness of personal queries, since you cannot join a set of
+   unrelated bugs together in a way that you wish.  Lists of bug numbers
+   can work, by they can only be used for small lists, and it is
+   impossible to share a list between multiple queries.
+
+   Personal keywords are necessary to replace personal tracking bugs, as
+   they would not pollute the keyword space.  Indeed, on many
+   installations this could remove some keywords out of the global
+   keyword space.
+
+   In a similar vein and with similar effects, group keywords could be
+   introduced that are only available to members of a specific group.
+
+  Keyword Restrictions
+
+   Keywords are not islands unto themselves.  Along with their potential
+   to be involved in the inter-field relationships mentioned earlier,
+   keywords can also be related to other keywords.
+
+   Essentially, there are two possibilities:
+     * a set of keywords are mutually exclusive
+     * the presence of a keyword implies another keyword must be present
+
+   Introduction of the ability to specify these restrictions would have
+   benefits.
+
+   If mutually exclusive keywords were present on a bug, their removal
+   would fix up the database, as well as reducing the number of keywords
+   on that bug.
+
+   In the situation where a keyword implies another keyword, there are
+   two possiblities as to how to handle the situation.
+
+   The first is automatically add the keyword.  This would fix up the
+   database, but it would increase the number of keywords on a bug.
+
+   The second is to automatically remove the keyword, and alter queries
+   so they pick up the first keyword as well as the removed keyword.
+   This would fix up the database and reduce the number of keywords on a
+   bug, but it might confuse users who don't see the keyword.
+   Alternatively, the implied keywords could be listed separately.
+
+Notifications
+
+   Every time a bug gets changed notifications get sent out to people
+   letting them know about what changes have been made.  This is a
+   significant feature, and all sorts of questions can be raised, but
+   they mainly boil down to when they should be sent and what they should
+   look like.
+
+  Changes You're Interested In
+
+   As of version 2.12 users can specify what sort of changes they are
+   interested in receiving notifications for.  However, this is still
+   limited.  As yet there is no facility to specify which keywords you
+   care about, and whether you care about changes to fields such as the
+   QA contact changes.
+   Furthermore, often an unnecessary comment will go along with a change,
+   either because it is required, or the commenter is ignorant of how the
+   new system works.  While explaining why you did something is useful,
+   merely commenting on what you did is not because that information is
+   already accessible view "Bug Activity".
+
+   Because of this unnecessary comment, a lot of changes that would
+   otherwise not generate notifications for certain people do so, because
+   few people are willing to turn off comments.  One way to deal with
+   this problem is to allow people to specify that their comments are
+   purely explanatory, and that anyone who is not interested in the
+   change will not be interested in the comment.
+
+   Furthermore, one possible rationale for unnecessary comments is that
+   the bug activity does not display on the normal page and hence it is
+   difficult to cross reference comments and actions.  Hence, it would be
+   beneficial to be able to do this.
+
+  Bugs You're Watching
+
+   Currently to receive a notification about a bug you need to have your
+   name on it.  This is suboptimal because you need to know about a bug
+   before you can receive notifications on it.  Often you are interested
+   in any bug with a field set to a specific value.  For example, you
+   might be interested in all bugs with a specific product, component or
+   keyword.
+
+   If someone could automatically receive notifications about these bugs,
+   it would make everyone's lives easier.  Currently the default assignee
+   and QA contact for a component will automatically receive
+   notifications for
+
+   Question:  This moves half way to a BCC.
+
+  Bulk Changes
+
+   A very useful feature of Bugzilla is the ability to perform an action
+   on multiple bugs at once.  However, this means that similar
+   notifications are currently generated for each bug modified.
+
+   This can result in a torrent of notifications that can annoy.
+
+   Furthermore, since the bugs are all changed close to each other in
+   time, it is easy for someone to mass delete all the notifications
+   generated by a bulk change and miss an unrelated notification in the
+   middle.
+
+   These factors can lead to a tendency for people to delay bulk changes,
+   or avoid them entirely.  This is suboptimal.
+
+   It would be better if a bulk change generated only one notification
+   mail.  This would vastly reduce the annoyance factor, and prevent
+   accidental deletion of notifications.
+
+   One problem with this change is that some people separate out
+   notifications using filtering.  This means that they would no longer
+   be match parts of a bulk change under different filtering rules.
+
+   One possibility to resolve this is to allow people to specify groups
+   of bugs.  All bugs within a group would go into the same
+   notification.  The filters could then distinguish the different bug
+   groups.
+
+   In any case, it is likely there would need to be a transition period
+   to allow people to alter their filters.
+
+Nominations
+
+   ?
+
+Linking Bugzilla Installations
+
+   The first example of linking Bugzilla installations together has is
+   the introduction of bug moving in version 2.12.  However, it would be
+   useful to be able to link installations in more ways.
+     * Dependencies and other relationships between bugs in other
+       installations.  This is difficult because dependencies are
+       synchronised on both bugs, so the installation that changes
+       dependencies would need to communicate the new state to the other
+       installation.  It would also mean that relationships and
+       notifications that refer to other bugs would need to communicate
+       with the other installation.
+     * References to bugs in other installations.  Currently if you type
+       "bug XXX" or "bug #XXX" where XXX is a number, you get an
+       automatic hyperlink to that bug.  It would be useful if you could
+       say "YYY bug #XXX" where YYY is the name of another installation.
+
+Retirement
+
+   ?
+
+Whiny Reports
+
+   ?
+
+  Group Redesign
+
+   ?
+
+  Hard Wrapping Comments
+
+   Currently Bugzilla "hard wraps" its comments to a specific line size,
+   similar to E-Mail.  This has various problems:
+     * The way it currently works, wrapping is done in the browser at
+       submission time using a non-standard HTML extension not supported
+       by some (uncommon) browsers.  These browsers generate comments
+       that scroll off the right side of the screen.
+     * Because comments are of fixed width, when you expand your browser
+       window, the comments do not expand to fit available space.
+
+   It would be much better to move to a world of soft wrapping, where the
+   browser wraps the text at display time, similar to a world processor.
+    And as in a word processor, soft wrapping does not preclude the
+   insertion of newlines.
+
+   Hard wrapping is too entrenched into text E-Mail to fix, but we can
+   fix Bugzilla without causing any problems.  The old content will still
+   be wrapped too early, but at least new content will work.
+

Appendix A. The Bugzilla FAQChapter 7. Bugzilla Variants and Competitors
I created this section to answer questions about Bugzilla + competitors and variants, then found a wonderful site which covers + an awful lot of what I wanted to discuss. Rather than quote it in + its entirety, I'll simply refer you here: http://linas.org/linux/pm.html
1. General Questions
A.1.1. Where can I find information about Bugzilla?
A.1.2. What license is Bugzilla distributed under? -
A.1.3. How do I get commercial support for Bugzilla? -
A.1.4. What major companies or projects are currently using Bugzilla - for bug-tracking? -
A.1.5. Who maintains Bugzilla? -
7.1. Red Hat Bugzilla
Red Hat Bugzilla is probably the most popular Bugzilla variant + on the planet. One of the major benefits of Red Hat Bugzilla is + the ability to work with Oracle, MySQL, and PostGreSQL databases + serving as the back-end, instead of just MySQL. Dave Lawrence + has worked very hard to keep Red Hat Bugzilla up-to-date, and + many people prefer the snappier-looking page layout of Red Hat + Bugzilla to the default Mozilla-standard formatting. +
URL: http://bugzilla.redhat.com/bugzilla/
7.2. Loki Bugzilla (Fenris)
Fenris can be found at http://fenris.lokigames.com. It is a fork from Bugzilla.
7.3. Issuezilla
Issuezilla is another fork from Bugzilla, and seems nearly + as popular as the Red Hat Bugzilla fork. Some Issuezilla team + members are regular contributors to the Bugzilla mailing + list/newsgroup. Issuezilla is not the primary focus of + bug-tracking at tigris.org, however. Their Java-based + bug-tracker, Scarab, a newfangled Java-based issue tracker, is under heavy development + and looks promising!
URL: http://issuezilla.tigris.org/servlets/ProjectHome
7.4. Scarab
Scarab is a promising new bug-tracking system built using + Java Serlet technology. As of this writing, no source code has + been released as a package, but you can obtain the code from + CVS. +
URL: http://scarab.tigris.org
7.5. Perforce SCM
Although Perforce isn't really a bug tracker, it can be used + as such through the "jobs" functionality.
http://www.perforce.com/perforce/technotes/note052.htmlhttp://www.perforce.com/perforce/technotes/note052.html
7.6. SourceForge
SourceForge is more of a way of coordinating geographically + distributed free software and open source projects over the + Internet than strictly a bug tracker, but if you're hunting for + bug-tracking for your open project, it may be just what the + software engineer ordered!
URL: http://www.sourceforge.net
Appendix A. The Bugzilla FAQ
1. General Questions
A.1.1. Where can I find information about Bugzilla?
A.1.2. What license is Bugzilla distributed under? +
A.1.3. How do I get commercial support for Bugzilla? +
A.1.4. What major companies or projects are currently using Bugzilla + for bug-tracking? +
A.1.5. Who maintains Bugzilla? +
A.1.6. How does Bugzilla stack up against other bug-tracking databases?
A.1.7. How do I change my user name in Bugzilla?
A.1.8. Why doesn't Bugzilla offer this or that feature or compatability with this other tracking software?
A.1.9. Why MySQL? I'm interested in seeing Bugzilla run on Oracle/Sybase/Msql/PostgreSQL/MSSQL?
A.1.10. Why do the scripts say "/usr/bonsaitools/bin/perl" instead of "/usr/bin/perl" or something else?
A.2.1. What about Red Hat Bugzilla?
A.2.2. What are the primary benefits of Red Hat Bugzilla?
A.2.3. What's the current status of Red Hat Bugzilla?
A.3.1. What is Loki Bugzilla (Fenris)?
A.4.1. Is Bugzilla web-based or do you have to have specific software or specific operating system on your machine?
A.4.2. Has anyone you know of already done any Bugzilla integration with Perforce (SCM software)?
A.4.3. Does Bugzilla allow the user to track multiple projects?
A.4.4. If I am on many projects, and search for all bugs assigned to me, will Bugzilla list them for me and allow me to sort by project, severity etc?
A.4.5. Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes, are there any that are NOT allowed?
A.4.6. Does Bugzilla allow us to define our own priorities and levels? Do we have complete freedom to change the labels of fields and format of them, and the choice of acceptable values? @@ -10043,7 +11229,7 @@ HREF="#AEN1809" >
A.4.7. The index.html page doesn't show the footer. It's really annoying to have to go to the querypage just to check my "my bugs" link. How do I get a footer on static HTML pages? @@ -10051,35 +11237,35 @@ HREF="#AEN1814" >
A.4.8. Does Bugzilla provide any reporting features, metrics, graphs, etc? You know, the type of stuff that management likes to see. :)
A.4.9. Is there email notification and if so, what do you see when you get an email? Do you see bug number and title or is it only the number?
A.4.10. Can email notification be set up to send to multiple people, some on the To List, CC List, BCC List etc?
A.4.11. If there is email notification, do users have to have any particular type of email application?
A.4.12. If I just wanted to track certain bugs, as they go through life, can I set it up to alert me via email whenever that bug changes, whether it be owner, status or description etc.? @@ -10087,7 +11273,7 @@ HREF="#AEN1845" >
A.4.13. Does Bugzilla allow data to be imported and exported? If I had outsiders write up a bug report using a MS Word bug template, could that template be imported into "matching" fields? If I wanted to take the results of a query @@ -10096,75 +11282,67 @@ HREF="#AEN1850" >
A.4.14. Does Bugzilla allow fields to be added, changed or deleted? If I want to - customize the bug submission form to meet our needs, can I do that using our - terminology? -
A.4.15. Has anyone converted Bugzilla to another language to be used in other countries? Is it localizable?
A.4.16. A.4.15. Can a user create and save reports? Can they do this in Word format? Excel format?
A.4.17. A.4.16. Can a user re-run a report with a new project, same query?
A.4.18. A.4.17. Can a user modify an existing report and then save it into another name?
A.4.19. A.4.18. Does Bugzilla have the ability to search by word, phrase, compound search?
A.4.20. A.4.19. Can the admin person establish separate group and individual user privileges?
A.4.21. A.4.20. Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use or how are they notified?
A.4.22. A.4.21. Are there any backup features provided?
A.4.23. A.4.22. Can users be on the system while a backup is in progress?
A.4.24. A.4.23. What type of human resources are needed to be on staff to install and maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of @@ -10173,8 +11351,8 @@ HREF="#AEN1909"
A.4.25. A.4.24. What time frame are we looking at if we decide to hire people to install and maintain the Bugzilla? Is this something that takes hours or weeks to install and a couple of hours per week to maintain and customize or is this @@ -10183,8 +11361,8 @@ HREF="#AEN1916"
A.4.26. A.4.25. Is there any licensing fee or other fees for using Bugzilla? Any out-of-pocket cost other than the bodies needed as identified above?
A.5.1. How do I download and install Bugzilla?
A.5.2. How do I install Bugzilla on Windows NT?
A.5.3. Is there an easy way to change the Bugzilla cookie name?
A.6.1. How do I completely disable MySQL security if it's giving me problems (I've followed the instructions in the installation section of this guide!)?
A.6.2. Are there any security problems with Bugzilla?
A.6.3. I've implemented the security fixes mentioned in Chris Yeh's security advisory of 5/10/2000 advising not to run MySQL as root, and am running into problems with MySQL no longer working correctly. @@ -10257,48 +11435,48 @@ HREF="#FAQ_EMAIL" >
A.7.1. I have a user who doesn't want to receive any more email from Bugzilla. How do I stop it entirely for this user?
A.7.2. I'm evaluating/testing Bugzilla, and don't want it to send email to anyone but me. How do I do it?
A.7.3. I want whineatnews.pl to whine at something more, or other than, only new bugs. How do I do it?
A.7.4. I don't like/want to use Procmail to hand mail off to bug_email.pl. What alternatives do I have?
A.7.5. How do I set up the email interface to submit/change bugs via email?
A.7.6. Email takes FOREVER to reach me from bugzilla -- it's extremely slow. What gives?
A.7.7. How come email never reaches me from bugzilla changes?
A.8.1. I've heard Bugzilla can be used with Oracle?
A.8.2. Bugs are missing from queries, but exist in the database (and I can pull them up by specifying the bug ID). What's wrong?
A.8.3. I think my database might be corrupted, or contain invalid entries. What do I do?
A.8.4. I want to manually edit some entries in my database. How?
A.8.5. I try to add myself as a user, but Bugzilla always tells me my password is wrong.
A.8.6. I think I've set up MySQL permissions correctly, but bugzilla still can't connect.
A.8.7. How do I synchronize bug information among multiple different Bugzilla databases?
A.8.8. Why do I get bizarre errors when trying to submit data, particularly problems with "groupset"?
A.8.9. How come even after I delete bugs, the long descriptions show up?
A.9.1. What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?
A.9.2. Is there a "Bundle::Bugzilla" equivalent for Win32?
A.9.3. CGI's are failing with a "something.cgi is not a valid Windows NT application" error. Why?
A.9.4. Can I have some general instructions on how to make Bugzilla on Win32 work?
A.9.5. I'm having trouble with the perl modules for NT not being able to talk to to the database.
A.10.1. The query page is very confusing. Isn't there a simpler way to query?
A.10.2. I'm confused by the behavior of the "accept" button in the Show Bug form. Why doesn't it assign the bug to me when I accept it?
A.10.3. I can't upload anything into the database via the "Create Attachment" link. What am I doing wrong?
A.10.4. Email submissions to Bugzilla that have attachments end up asking me to save it as a "cgi" file.
A.10.5. How do I change a keyword in Bugzilla, once some bugs are using it?
A.11.1. What bugs are in Bugzilla right now?
A.11.2. How can I change the default priority to a null value? For instance, have the default priority be "---" instead of "P2"?
A.11.3. What's the best way to submit patches? What guidelines should I follow?
A.1.1.
A.1.2.
A.1.3.
A.1.4.
A.1.5.
A.1.6.
A.1.7.
A.1.8.
A.1.9. Terry Weissman answers,
A.1.10.
Here's Terry Weissman's comment, for some historical context:
A.2.1.
Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions:
A.2.2. Dave Lawrence:
A.2.3. Dave Lawrence:
A.3.1.
A.4.1.
A.4.2.
A.4.3.
A.4.4.
A.4.5.
A.4.6.
There is no GUI for adding fields to Bugzilla at this + time. You can follow development of this feature at + http://bugzilla.mozilla.org/show_bug.cgi?id=91037 +
A.4.7.
This was a late-breaking question for the Guide, so I just have to - quote the relevant newsgroup thread on it. -
It's possible to get the footer on the static index page using + Server Side Includes (SSI). The trick to doing this is making + sure that your web server is set up to allow SSI and specifically, + the #exec directive. You should also rename index.html + to index.shtml. +
> AFAIK, most sites (even if they have SSI enabled) won't have #exec cmd
-> enabled.  Perhaps what would be better is a #include virtual and a
-> footer.cgi the basically has the "require 'CGI.pl' and PutFooter command.
->
-> Please note that under most configurations, this also requires naming
-> the file from index.html to index.shtml (and making sure that it will
-> still be reconized as an index).  Personally, I think this is better on
-> a per-installation basis (perhaps add something to the FAQ that says how
-> to do this).
-
-Good point.  Yeah, easy enough to do, that it shouldn't be a big deal for
-someone to take it on if they want it.  FAQ is a good place for it.
-
-> Dave Miller wrote:
->
->> I did a little experimenting with getting the command menu and footer on
->> the end of the index page while leaving it as an HTML file...
->>
->> I was successful. :)
->>
->> I added this line:
->>
->>
->>
->> Just before the </BODY> </HTML> at the end of the file.  And it worked.
->>
->> Thought I'd toss that out there.  Should I check this in?  For those that
->> have SSI disabled, it'll act like a comment, so I wouldn't think it would
->> break anything.
-
After you've done all that, you can add the following line to + index.shtml: +

+
This line will be replaced with the actual HTML for the footer + when the page is requested, so you should put this line where you + want the footer to appear. +
Because this method depends on being able to use a #exec directive, + and most ISP's will not allow that, there is an alternative method. + You could have a small script (such as api.cgi) + that basically looks like: +
#!/usr/bonsaitools/bin/perl -w + +require 'globals.pl'; + +if ($::FORM{sub} eq 'PutFooter') { + PutFooter(); +} else { + die 'api.cgi was incorrectly called'; +}
+ and then put this line in index.shtml. +

+

This still requires being able to use Server Side Includes, if + this simply will not work for you, see bug 80183 + for a third option. +
A.4.8.
A.4.9.
A.4.10.
A.4.11.
A.4.12.
A.4.13.
As for data import, any application can send data to Bugzilla through - the HTTP protocol, or through Mozilla's XML API. However, it seems - kind of silly to put another front-end in front of Bugzilla; - it makes more sense to create a simplified bug submission form in - HTML. You can find an excellent example at - http://www.mozilla.org/quality/help/bugzilla-helper.html -
A.4.14. Does Bugzilla allow fields to be added, changed or deleted? If I want to - customize the bug submission form to meet our needs, can I do that using our - terminology? -
Yes. -
As for data import, any application can send data to Bugzilla through + the HTTP protocol, or through Mozilla's XML API. However, it seems + kind of silly to put another front-end in front of Bugzilla; + it makes more sense to create a simplified bug submission form in + HTML. You can find an excellent example at + http://www.mozilla.org/quality/help/bugzilla-helper.html +
A.4.15. A.4.14. Has anyone converted Bugzilla to another language to be used in other countries? Is it localizable?
A.4.16. A.4.15. Can a user create and save reports? Can they do this in Word format? Excel format?
A.4.17. A.4.16. Can a user re-run a report with a new project, same query?
A.4.18. A.4.17. Can a user modify an existing report and then save it into another name?
A.4.19. A.4.18. Does Bugzilla have the ability to search by word, phrase, compound search?
A.4.20. A.4.19. Can the admin person establish separate group and individual user privileges?
A.4.21. A.4.20. Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use or how are they notified? @@ -12002,10 +13284,10 @@ CLASS="QANDAENTRY" CLASS="QUESTION" >
A.4.22. A.4.21. Are there any backup features provided?
A.4.23. A.4.22. Can users be on the system while a backup is in progress?

A.4.24. A.4.23. What type of human resources are needed to be on staff to install and maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of @@ -12093,10 +13375,10 @@ CLASS="QANDAENTRY" CLASS="QUESTION" >

A.4.25. A.4.24. What time frame are we looking at if we decide to hire people to install and maintain the Bugzilla? Is this something that takes hours or weeks to install and a couple of hours per week to maintain and customize or is this @@ -12124,10 +13406,10 @@ CLASS="QANDAENTRY" CLASS="QUESTION" >

A.4.26. A.4.25. Is there any licensing fee or other fees for using Bugzilla? Any out-of-pocket cost other than the bodies needed as identified above?

A.5.1.

A.5.2.

A.5.3.

A.6.1.

A.6.2.

A.6.3.

A.7.1.

A.7.2.

A.7.3.

A.7.4. You can call bug_email.pl directly from your aliases file, with an entry like this:

A.7.5.
A.7.6. If you are using an alternate Mail Transport Agent (MTA other than sendmail), make sure the options given in the "processmail" script for all - instances of "sendmail" are correct for your MTA. If you are using Sendmail, - you may wish to delete the "-ODeliveryMode=deferred" option in the - "processmail" script for every invocation of "sendmail". (Be sure and leave - the "-t" option, though!) -
A better alternative is to change the "-O" option to - "-ODeliveryMode=background". This prevents Sendmail from hanging your - Bugzilla Perl processes if the domain to which it must send mail - is unavailable. + instances of "sendmail" are correct for your MTA.
This is now a configurable parameter called "sendmailnow", available - from editparams.cgi. +> If you are using Sendmail, try enabling "sendmailnow" in editparams.cgi. + If you are using Postfix, you will also need to enable "sendmailnow".

A.11.1. Try this link to view current bugs or requests for enhancement for Bugzilla.

You can view bugs marked for 2.14 release +> You can view bugs marked for 2.16 release here. - This list includes bugs for the 2.14 release that have already + This list includes bugs for the 2.16 release that have already been fixed and checked into CVS. Please consult the

The Bugzilla Guide
Prev	Appendix D. Useful Patches and Utilities for Bugzilla	Next

cvn{}|/setjn{{statusdict +/jobname known{statusdict/jobname 3 -1 $ put}if}stopped cleartomark}b/solid{[] +0 setdash}b/setdsh{0 setdash}b/colspRefresh{}b/rp{4 2 $ M 1 ^ 0 - 0 ~ - neg 0 +-}b/rr{1 ^ 0 - 0 ~ - neg 0 - C}b +%%EndResource +%%BeginResource: file Pscript_Win_Utils_L1 2.0 0 +L2? not g{/rf{N rp L}b/fx{1 1 dtransform @ 0 ge{1 sub 1}{1 add -0.25}? 3 -1 $ +@ 0 ge{1 sub 1}{1 add -0.25}? 3 1 $ 4 1 $ idtransform 4 -2 $ idtransform}b/BZ{ +4 -2 $ snap + +S fx rf}b/rs{N rp C K}b/rc{N rp clip N}b/sg{setgray}b/sco{ +setrgbcolor}b/sgco{{sg}{sco}?}b}e +%%EndResource +%%BeginResource: file Pscript_Win_Utils_L2 2.0 0 +L2? g{/colspA/DeviceGray |/colspABC/DeviceRGB |/setAorABC{{colspA}{colspABC}? +setcolorspace}b/rf/rectfill , |/fx{1 1 dtransform @ 0 ge{1 sub 0.5}{1 add -0.5 +}? 3 -1 $ @ 0 ge{1 sub 0.5}{1 add -0.5}? 3 1 $ 4 1 $ idtransform 4 -2 $ +idtransform}b/BZ{4 -2 $ snap + +S fx rf}b/rs/rectstroke , |/rc/rectclip , |/sg +{@ @ setcolor}b/sco{setcolor}b/colspRefresh{colspABC setcolorspace}b/sgco{{sg +}{sco}?}b/UtilsInit{F setglobal}b/definecolorrendering{/ColorRendering +defineresource !}b/findcolorrendering{@/ColorRendering resourcestatus{! ! +/ColorRendering findresource T}{! F}?}b/selectcolorrendering{@/ColorRendering +resourcestatus{! !/ColorRendering}{!/DefaultColorRendering/ColorRendering}? +findresource setcolorrendering}b}e +%%EndResource +end +%%EndProlog + +%%BeginSetup +[ 1.000 0 0 1.000 0 0 ] false Pscript_Win_Driver_Incr dup /initialize get exec + +[{0 +/languagelevel where{pop languagelevel}{1}ifelse 2 ge{1 dict dup/JobTimeout 4 -1 roll put setuserparams}{statusdict/setjobtimeout get exec}ifelse +} stopped cleartomark +[{240 +/languagelevel where{pop languagelevel}{1}ifelse 2 ge{1 dict dup/WaitTimeout 4 -1 roll put setuserparams}{statusdict/waittimeout 3 -1 roll put}ifelse +} stopped cleartomark +[{ +%%BeginFeature: *Print as Grayscale No + + <> setpagedevice +%%EndFeature +} stopped cleartomark +[{ + +} stopped cleartomark +[{ +%%BeginFeature: *InputSlot AutoSelect Tray + +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *PageSize Letter + + <> setpagedevice + 2 dict dup /PageSize [612 792] put dup /ImagingBBox null put setpagedevice +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *ColorSmart Text Vivid Color + + globaldict /ColorSmartColorMatching known + { true ColorSmartColorMatching } if + globaldict /ColorSmartColorMatching known + { Vivid ColorSmartTextAdjustment } if + +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *ColorSmart Graphics Vivid Color + + globaldict /ColorSmartColorMatching known + { Vivid ColorSmartGraphicsAdjustment } if + +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *ColorSmart Photos Match Color Across Printers + + globaldict /ColorSmartColorMatching known + { MatchScreen ColorSmartImageAdjustment } if + +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *Text Halftone Detail + + globaldict /ColorSmartColorMatching known + { Detail ColorSmartTextHalftone } if + +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *Graphics Halftone Smooth + + globaldict /ColorSmartColorMatching known + { Smooth ColorSmartGraphicsHalftone } if + +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *Image Halftone Smooth + + globaldict /ColorSmartColorMatching known + { Smooth ColorSmartImageHalftone } if + +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *ColorSmart Auto + + globaldict /ColorSmartColorMatching known + { Vivid ColorSmartTextAdjustment } if + globaldict /ColorSmartColorMatching known + { Vivid ColorSmartGraphicsAdjustment } if + globaldict /ColorSmartColorMatching known + { MatchScreen ColorSmartImageAdjustment } if + globaldict /ColorSmartColorMatching known + { Detail ColorSmartTextHalftone } if + globaldict /ColorSmartColorMatching known + { Smooth ColorSmartGraphicsHalftone } if + globaldict /ColorSmartColorMatching known + { Smooth ColorSmartImageHalftone } if + /setscreen { pop pop pop } def + /setcolorscreen { pop pop pop pop pop pop pop pop pop pop pop pop } def + globaldict /ColorSmartColorMatching known + {true ColorSmartColorMatching } if + +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *OutputBin Upper +1 dict dup /OutputFaceUp false put setpagedevice +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *MediaType Plain Paper + +%%EndFeature +} stopped cleartomark +1 setlinecap 1 setlinejoin +/mysetup [ 0.240 0 0 -0.240 12.000 779.000 ] | +%%EndSetup + +userdict begin /savelevel0 save def end +%%Page: 1 1 +%%BeginPageSetup +[{ +%%BeginFeature: *Rear Feed Unit Not Installed + +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *VMOption 36 - 43 MB RAM + +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *Resolution 300dpi + +%%EndFeature +} stopped cleartomark +[{ +%%BeginFeature: *Duplex + +%%EndFeature +} stopped cleartomark +userdict begin /pagesave save def end mysetup concat colspRefresh : 1.000 1.000 1.000 sco 0 0 2550 3300 rf ; +%%EndPageSetup + +: 0 0 2454 3191 rc pagesave restore +Pscript_Win_Driver_Incr begin +%%BeginResource: file Pscript_Win_Graphics 2.0 0 +/SavedCTM null |/CTMsave{/SavedCTM SavedCTM currentmatrix |}b/CTMrestore{ +SavedCTM setmatrix}b/mp null |/ADO_mxRot null |/GDIHMatrix null | +/GDIHPatternDict 22 dict | GDIHPatternDict `/PatternType 1 |/PaintType 2 | +/Reps L2?{1}{5}? |/XStep 8 Reps mul |/YStep XStep |/BBox[0 0 XStep YStep]| +/TilingType 1 |/PaintProc{` 1 Lw[]0 setdash PaintData , exec E}b/FGnd null | +/BGnd null |/HS_Horizontal{horiz}b/HS_Vertical{vert}b/HS_FDiagonal{fdiag}b +/HS_BDiagonal{biag}b/HS_Cross{horiz vert}b/HS_DiagCross{fdiag biag}b/MaxXYStep +XStep YStep gt{XStep}{YStep}? |/horiz{Reps{0 4 M XStep 0 - 0 8 +}repeat 0 -8 +Reps mul + K}b/vert{Reps{4 0 M 0 YStep - 8 0 +}repeat 0 -8 Reps mul + K}b/biag +{Reps{0 0 M MaxXYStep @ - 0 YStep neg M MaxXYStep @ - 0 8 +}repeat 0 -8 Reps +mul + 0 YStep M 8 8 - K}b/fdiag{Reps{0 0 M MaxXYStep @ neg - 0 YStep M +MaxXYStep @ neg - 0 8 +}repeat 0 -8 Reps mul + MaxXYStep @ M 8 -8 - K}b E +/makehatch{GDIHPatternDict/PaintData 3 -1 $ put CTMsave GDIHMatrix setmatrix +GDIHPatternDict matrix mp CTMrestore ~ U ~ 2 ^ put}b/h0{/h0/HS_Horizontal +makehatch}b/h1{/h1/HS_Vertical makehatch}b/h2{/h2/HS_FDiagonal makehatch}b/h3{ +/h3/HS_BDiagonal makehatch}b/h4{/h4/HS_Cross makehatch}b/h5{/h5/HS_DiagCross +makehatch}b/GDIBWPatternDict 17 dict @ `/PatternType 1 |/PaintType L2?{1}{2}? +|/RepsV L2?{1}{6}? |/RepsH L2?{1}{5}? |/BBox[0 0 RepsH 1]|/TilingType 1 | +/XStep 1 |/YStep 1 |/Height 8 RepsV mul |/Width 8 |/mx[Width 0 0 Height neg 0 +Height]|/FGnd null |/BGnd null |/SetBGndFGnd L2?{{BGnd null ne{BGnd aload ! +sgco BBox aload ! 2 ^ sub ~ 3 ^ sub ~ rf}if FGnd null ne{FGnd aload ! sgco}if} +}{{}}? b/PaintProc{` SetBGndFGnd RepsH{Width Height F mx PaintData imagemask +Width 0 +}repeat E}b E |/GDIBWPatternMx null |/pfprep{save 4 1 $ +/PatternOfTheDay 4 1 $ GDIBWPatternDict `/PaintData ~ |/BGnd ~ |/FGnd ~ | E +CTMsave GDIBWPatternMx setmatrix GDIBWPatternDict matrix mp CTMrestore ~ !}b +/hrf null |/prf{pfprep ~ 6 1 $ 5 hrf restore}b/GraphInit{GDIHMatrix null eq{ +/SavedCTM matrix | : ADO_mxRot concat 0 0 snap + : 0.48 @ GDIHPatternDict ` +YStep mul ~ XStep mul ~ dsnap YStep V ~ XStep V ~ E +S/GDIHMatrix matrix +currentmatrix readonly | ; : 0.24 -0.24 +S GDIBWPatternDict ` Width Height E +dsnap +S/GDIBWPatternMx matrix currentmatrix readonly | ; ;}if}b/cirp{360 0 An +C}b/ellp{CTMsave + +S 0.5 0 M 0 0 0.5 360 0 An C CTMrestore}b/rrp{/rad ~ |/y2 +~ |/x2 ~ |/y1 ~ |/x1 ~ | x2 x1 add 2 V y1 M x1 y1 x1 y2 rad arct x1 y2 x2 y2 +rad arct x2 y2 x2 y1 rad arct x2 y1 x1 y1 rad arct C}b/RRp{CTMsave + +S/dyS ~ +|/dxS ~ | dxS 2 V 0 M 0 0 0 dyS 0.5 arct 0 dyS dxS dyS 0.5 arct dxS dyS dxS 0 +0.5 arct dxS 0 0 0 0.5 arct C CTMrestore}b +%%EndResource + +%%BeginResource: file Pscript_Win_Graphics_L1 2.0 0 +L2? not g{/arct{arcto ! ! ! !}b/GDIpattfill{@ ` BGnd null ne PaintType 2 eq +and{: BGnd aload ! sgco fEOFill{O}{L}? ; FGnd aload ! U/fGray 2 ^ put{2}{4}? +-1 $}if E @ patterncalc : 4 ^/PaintType get 2 eq{fGray{6 -1 $ sg}{8 -3 $ sco}? +}if fEOFill{eoclip}{clip}? N patternfill ; N}b/hrf{/fGray 1 ^ 6 eq | -4 $ N rp +C/fEOFill F | GDIpattfill}b/hfMain{/fEOFill ~ |/fGray ~ | GDIpattfill}b/hf{T +hfMain}b/hfW{F hfMain}b/hs{currentpoint strokepath M hfW}b/pfMain{/fEOFill ~ | +pfprep GDIpattfill restore N}b/pf{T pfMain}b/pfW{F pfMain}b/ps{currentpoint +strokepath M pfW}b/mpstr 1 string |/mp{~ @ length 12 add dict copy ` +/PatternCTM matrix currentmatrix |/PatternMatrix ~ |/PatWidth XStep mpstr +length mul |/PatHeight YStep |/FontType 3 |/Encoding 256 array | 3 string 0 1 +255{Encoding ~ @ 3 ^ cvs cvn put}for !/FontMatrix matrix |/FontBBox BBox | +/BuildChar{! @ ` XStep 0 FontBBox aload ! setcachedevice/PaintProc , E : exec +;}b & E ~ @ 3 -1 $ definefont}b/patterncalc{` : PatternCTM setmatrix +PatternMatrix concat BBox aload ! ! ! + pathbbox ; PatHeight V ceiling 4 1 $ +PatWidth V ceiling 4 1 $ PatHeight V floor 4 1 $ PatWidth V floor 4 1 $ 2 ^ +sub cvi abs ~ 3 ^ sub cvi abs ~ 4 2 $ PatHeight mul ~ PatWidth mul ~ E}b +/patternfill{5 -1 $ @ ` Ji PatternCTM setmatrix PatternMatrix concat 0 2 ^ 2 ^ +M 0 1 mpstr length 1 sub{1 ^ mpstr 3 1 $ put}for ! 2 ^{currentpoint 5 ^{mpstr +S}repeat YStep add M}repeat ! ! ! ! E}b}e +%%EndResource + +%%BeginResource: file Pscript_Win_Graphics_L2 2.0 0 +L2? g{/mp/makepattern , |/hrf{6 eq setAorABC setpattern rectfill}b/hf{ +setAorABC setpattern O}b/hfW{setAorABC setpattern L}b/hs{setAorABC setpattern +K}b/pf{pfprep setpattern O restore N}b/pfW{pfprep setpattern L restore N}b/ps{ +pfprep setpattern K restore N}b}e +%%EndResource + +end reinitialize +userdict begin /pagesave save def end mysetup concat colspRefresh +: 0 0 0 sco 1 Lc 1 Lj solid 0 0 2454 3191 rc +1989 1646 N M 0 -419 - 1 Lw solid 0 0 0 sco K ; +N 1968.500 1645.500 19.500 88.603 -1.397 An +1 Lw 1 Lc 1 Lj 0 0 0 sco K : 0 0 2454 3191 rc +1931 1666 N M 38 0 - 0 0 0 sco K ; +N 1930.500 1685.500 19.500 -88.531 175.601 An +0 0 0 sco K : 0 0 2454 3191 rc +1911 2275 N M 0 -589 - 0 0 0 sco K ; : 1818 1632 636 23 rc : 1.000 1.000 1.000 sco 1872 1632 156 23 rf ; pagesave restore +Pscript_Win_Driver_Incr begin +%%BeginResource: file Pscript_Win_Encoding 2.0 0 +/bullets{{/bullet}repeat}b/ANSIEncoding[/grave/acute/circumflex/tilde/macron +/breve/dotaccent/dieresis/ring/cedilla/hungarumlaut/ogonek/caron/dotlessi 18 +bullets StandardEncoding 32 95 getinterval aload ! 3 bullets/quotesinglbase +/florin/quotedblbase/ellipsis/dagger/daggerdbl/circumflex/perthousand/Scaron +/guilsinglleft/OE 4 bullets/quoteleft/quoteright/quotedblleft/quotedblright +/bullet/endash/emdash/tilde/trademark/scaron/guilsinglright/oe 2 bullets +/Ydieresis/space/exclamdown/cent/sterling/currency/yen/brokenbar/section +/dieresis/copyright/ordfeminine/guillemotleft/logicalnot/hyphen/registered +/macron/degree/plusminus/twosuperior/threesuperior/acute/mu/paragraph +/periodcentered/cedilla/onesuperior/ordmasculine/guillemotright/onequarter +/onehalf/threequarters/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis +/Aring/AE/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute +/Icircumflex/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis +/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn/germandbls +/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla/egrave/eacute +/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis/eth/ntilde/ograve +/oacute/ocircumflex/otilde/odieresis/divide/oslash/ugrave/uacute/ucircumflex +/udieresis/yacute/thorn/ydieresis]| ANSIEncoding @ 39/quotesingle put 96/grave +put/ANSIEncodingOld ANSIEncoding 256 array copy | ANSIEncodingOld @[138 153 +154 169 172 174 177 178 179 181 185 188 189 190 208 215 221 222 240 247 253 +254]{/bullet put @}forall 166/bar put 176/ring put +%%EndResource + +%%BeginResource: file Pscript_Win_Text 2.0 0 +/TextInit{TextInitialised? not{/Pscript_Windows_Font & |/TextInitialised? T | +/fM[1 0 0 -1 0 0]|/mFM matrix |/iMat[1 0 0.212557 neg 1 0 0]|}if}b/xUP null | +/yUP null |/uW null |/xSP null |/ySP null |/sW null |/copyfont{1 ^ length add +dict `{1 ^/FID ne{|}{! !}?}forall & E}b/rF{3 copyfont @ `/Encoding +ANSIEncoding &/CharStrings known{CharStrings/Eth known not{! ANSIEncodingOld} +if}if | E}b/mF{findfont ~{@/Encoding get @ StandardEncoding eq{! T}{{ +ISOLatin1Encoding}stopped{! F}{eq}?{T}{@ ` T 32 1 127{Encoding 1 ^ get +StandardEncoding 3 -1 $ get eq and}for E}?}?}{F}?{rF}{3 copyfont}? ` +/OrigFontType ~ |/OrigFontName ~ | & E 2 ^ ~ definefont fM 5 4 -1 $ put fM 4 0 +put fM makefont Pscript_Windows_Font 3 1 $ put}b/xF{scalefont +Pscript_Windows_Font 3 1 $ put}b/xMF{mFM astore makefont Pscript_Windows_Font +3 1 $ put}b/xF2/scalefont , |/xMF2{mFM astore makefont}b/sLT{: Lw -M +currentpoint snap M 0 - 0 Lc K ;}b/sSU{N/uW ~ |/yUP ~ |/xUP ~ |}b/sU{xUP yUP +uW sLT}b/sST{N/sW ~ |/ySP ~ |/xSP ~ |}b/sT{xSP ySP sW sLT}b/sR{: + R 0 0 M}b +/sRxy{: matrix astore concat 0 0 M}b/eR/; , | +%%EndResource + +end reinitialize +userdict begin /pagesave save def end mysetup concat colspRefresh +: 0 0 0 sco 1 Lw 1 Lc 1 Lj 1818 1632 636 23 rc 0 0 0 sco %%IncludeFont: Helvetica +(F0) cvn +0.950 + (Helvetica) cvn /Type1 +T +(Helvetica) cvn +mF +(F0_20) cvn +F0 +20 +xF +F0_20 +Ji +1872 1632 M +-0.012 0 (product = product)A +; +1989 1304 N M 7 34 - -15 0 - 8 -34 - C : 0 0 0 sco O ; 1 Lw 1 Lc 1 Lj 0 0 0 sco K : 0 0 2454 3191 rc +2135 1050 N M -906 0 - 0 0 0 sco K ; : 1408 1060 1026 23 rc : 1.000 1.000 1.000 sco 1462 1060 164 23 rf ; 0 0 0 sco F0_20 +Ji +1462 1060 M +0.002 0 (product = program)A +; +1742 1050 N M -33 7 - 0 -15 - 33 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +2093 1250 N M -1848 0 - 0 0 0 sco K ; : 1014 1260 1026 23 rc : 1.000 1.000 1.000 sco 1068 1260 164 23 rf ; 0 0 0 sco F0_20 +Ji +1068 1260 M +0.002 0 (product = program)A +; +1742 1250 N M -33 7 - 0 -15 - 33 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +1798 1151 N M -946 0 - 0 0 0 sco K ; : 1204 1161 1026 23 rc : 1.000 1.000 1.000 sco 1258 1161 156 23 rf ; 0 0 0 sco F0_20 +Ji +1258 1161 M +-0.012 0 (product = product)A +; +1742 1151 N M -33 7 - 0 -15 - 33 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +717 1719 N M 0 689 - 0 0 0 sco K ; +N 736.500 1718.500 19.500 -88.531 175.601 An +0 0 0 sco K : 0 0 2454 3191 rc +864 1699 N M -127 0 - 0 0 0 sco K ; +N 863.500 1678.500 19.500 88.603 -1.397 An +0 0 0 sco K : 0 0 2454 3191 rc +884 1464 N M 0 215 - 0 0 0 sco K ; : 681 1687 918 23 rc : 1.000 1.000 1.000 sco 735 1687 130 23 rf ; 0 0 0 sco F0_20 +Ji +735 1687 M +-0.115 0 (userid = userid)A +; +717 2221 N M -8 -33 - 15 0 - -7 33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +649 1684 N M 0 737 - 0 0 0 sco K ; +N 628.500 1683.500 19.500 1.397 -91.469 An +0 0 0 sco K : 0 0 2454 3191 rc +334 1664 N M 295 0 - 0 0 0 sco K ; : 513 1635 918 23 rc : 1.000 1.000 1.000 sco 567 1635 130 23 rf ; 0 0 0 sco F0_20 +Ji +567 1635 M +-0.115 0 (userid = userid)A +; +649 2221 N M -8 -33 - 15 0 - -7 33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +837 1882 N M 0 378 - 0 0 0 sco K ; +N 856.500 1881.500 19.500 -88.531 175.601 An +0 0 0 sco K : 0 0 2454 3191 rc +1121 1862 N M -264 0 - 0 0 0 sco K ; : 0 0 2454 3191 rc +1467 1862 N M -346 0 - 0 0 0 sco K ; : 869 1850 756 23 rc : 1.000 1.000 1.000 sco 923 1850 113 23 rf ; 0 0 0 sco F0_20 +Ji +923 1850 M +-0.078 0 (userid = who)A +; +837 2221 N M -8 -33 - 15 0 - -7 33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +962 2267 N M -94 0 - 0 0 0 sco K ; +N 961.500 2246.500 19.500 88.603 -1.397 An +0 0 0 sco K : 0 0 2454 3191 rc +982 2105 N M 0 142 - 0 0 0 sco K ; +N 1001.500 2104.500 19.500 -88.531 175.601 An +0 0 0 sco K : 0 0 2454 3191 rc +1347 2085 N M -345 0 - 0 0 0 sco K ; : 872 2164 756 23 rc : 1.000 1.000 1.000 sco 926 2164 113 23 rf ; 0 0 0 sco F0_20 +Ji +926 2164 M +-0.078 0 (userid = who)A +; +872 2267 N M 33 -8 - 0 15 - -33 -7 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +978 2437 N M -158 0 - 0 0 0 sco K ; +N 977.500 2416.500 19.500 88.603 -1.397 An +0 0 0 sco K : 0 0 2454 3191 rc +998 2345 N M 0 72 - 0 0 0 sco K ; +N 1017.500 2344.500 19.500 -88.531 175.601 An +0 0 0 sco K : 0 0 2454 3191 rc +1212 2325 N M -194 0 - 0 0 0 sco K ; : 888 2369 756 23 rc : 1.000 1.000 1.000 sco 942 2369 113 23 rf ; 0 0 0 sco F0_20 +Ji +942 2369 M +-0.078 0 (userid = who)A +; +872 2437 N M 33 -7 - 0 15 - -33 -8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +829 2672 N M 0 -152 - 0 0 0 sco K ; +N 848.500 2671.500 19.500 178.531 85.815 An +0 0 0 sco K : 0 0 2454 3191 rc +1194 2692 N M -345 0 - 0 0 0 sco K ; : 700 2697 1242 23 rc : 1.000 1.000 1.000 sco 754 2697 184 23 rf ; 0 0 0 sco F0_20 +Ji +754 2697 M +-0.104 0 (userid = submitter_id)A +; +829 2620 N M 8 33 - -15 0 - 7 -33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +570 2708 N M 0 -156 - 0 0 0 sco K ; +N 589.500 2707.500 19.500 178.531 85.815 An +0 0 0 sco K : 0 0 2454 3191 rc +773 2728 N M -183 0 - 0 0 0 sco K ; +N 772.500 2747.500 19.500 1.397 -91.469 An +0 0 0 sco K : 0 0 2454 3191 rc +793 2836 N M 0 -88 - 0 0 0 sco K ; : 572 2716 756 23 rc : 1.000 1.000 1.000 sco 626 2716 113 23 rf ; 0 0 0 sco F0_20 +Ji +626 2716 M +-0.078 0 (userid = who)A +; +570 2620 N M 8 33 - -15 0 - 7 -33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +1554 2379 N M 690 0 - 0 0 0 sco K ; +N 1553.500 2358.500 19.500 178.531 85.815 An +0 0 0 sco K : 0 0 2454 3191 rc +1534 2032 N M 0 327 - 0 0 0 sco K ; : 1427 2384 918 23 rc : 1.000 1.000 1.000 sco 1481 2384 140 23 rf ; 0 0 0 sco F0_20 +Ji +1481 2384 M +-0.192 0 (bug_id = bug_id)A +; +1826 2379 N M -33 8 - 0 -15 - 33 7 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +1306 2476 N M 620 0 - 0 0 0 sco K ; +N 1305.500 2455.500 19.500 178.531 85.815 An +0 0 0 sco K : 0 0 2454 3191 rc +1286 2224 N M 0 232 - 0 0 0 sco K ; : 1179 2481 918 23 rc : 1.000 1.000 1.000 sco 1233 2481 140 23 rf ; 0 0 0 sco F0_20 +Ji +1233 2481 M +-0.192 0 (bug_id = bug_id)A +; +1826 2476 N M -33 8 - 0 -15 - 33 7 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +1693 2787 N M 140 0 - 0 0 0 sco K ; +N 1692.500 2766.500 19.500 178.531 85.815 An +0 0 0 sco K : 0 0 2454 3191 rc +1673 2652 N M 0 115 - 0 0 0 sco K ; +N 1652.500 2651.500 19.500 1.397 -91.469 An +0 0 0 sco K : 0 0 2454 3191 rc +1487 2632 N M 166 0 - 0 0 0 sco K ; : 1549 2697 905 23 rc : 1.000 1.000 1.000 sco 1603 2697 140 23 rf ; 0 0 0 sco F0_20 +Ji +1603 2697 M +-0.192 0 (bug_id = bug_id)A +; +1826 2787 N M -33 7 - 0 -15 - 33 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +1953 2954 N M -880 0 - 0 0 0 sco K ; : 1321 2964 918 23 rc : 1.000 1.000 1.000 sco 1375 2964 140 23 rf ; 0 0 0 sco F0_20 +Ji +1375 2964 M +-0.192 0 (bug_id = bug_id)A +; +1826 2954 N M -33 8 - 0 -15 - 33 7 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +326 2275 N M 314 0 - 0 0 0 sco K ; +N 325.500 2254.500 19.500 178.531 85.815 An +0 0 0 sco K : 0 0 2454 3191 rc +306 1933 N M 0 322 - 0 0 0 sco K ; : 204 2280 918 23 rc : 1.000 1.000 1.000 sco 258 2280 130 23 rf ; 0 0 0 sco F0_20 +Ji +258 2280 M +-0.115 0 (userid = userid)A +; +426 2275 N M -33 7 - -1 -15 - 34 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +224 2919 N M 0 -905 - 0 0 0 sco K ; : 107 2409 1026 23 rc : 1.000 1.000 1.000 sco 161 2409 126 23 rf ; 0 0 0 sco F0_20 +Ji +161 2409 M +-0.075 0 (fieldid = fieldid)A +; +224 2819 N M -7 -34 - 15 0 - -8 34 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +360 2910 N M 573 0 - 0 0 0 sco K ; : 555 2920 1026 23 rc : 1.000 1.000 1.000 sco 609 2920 126 23 rf ; 0 0 0 sco F0_20 +Ji +609 2920 M +-0.075 0 (fieldid = fieldid)A +; +542 2910 N M 34 -8 - 0 16 - -34 -8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +2070 2339 N M 0 -475 - 0 0 0 sco K ; : 1946 2044 508 23 rc : 1.000 1.000 1.000 sco 2000 2044 140 23 rf ; 0 0 0 sco F0_20 +Ji +2000 2044 M +-0.192 0 (bug_id = bug_id)A +; +2070 2227 N M -7 -33 - 15 0 - -8 33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc +1726 2297 N M 372 0 - 0 0 0 sco K ; +N 1725.500 2276.500 19.500 178.531 85.815 An +0 0 0 sco K : 0 0 2454 3191 rc +1706 1859 N M 0 418 - 0 0 0 sco K ; +N 1685.500 1858.500 19.500 1.397 -91.469 An +0 0 0 sco K : 0 0 2454 3191 rc +1537 1839 N M 149 0 - 0 0 0 sco K ; : 1582 2056 872 23 rc : 1.000 1.000 1.000 sco 1636 2056 140 23 rf ; 0 0 0 sco F0_20 +Ji +1636 2056 M +-0.192 0 (bug_id = bug_id)A +; +1826 2297 N M -33 8 - 0 -15 - 33 7 - C : 0 0 0 sco O ; 0 0 0 sco K +174 1137 N M 416 206 rr : 1.000 1.000 1.000 sco O ; 0 Lc 0 Lj 0 0 0 sco K : 235 1142 345 32 rc 0 0 0 sco (F0_27) cvn +F0 +27 +xF +F0_27 +Ji +308 1142 M +0.093 0 (components)A +; : 0 0 2454 3191 rc +174 1177 N M 416 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 184 1180 196 32 rc 0 0 0 sco F0_27 +Ji +184 1180 M +-0.106 0 (value)A +; : 400 1180 190 32 rc 0 0 0 sco F0_27 +Ji +400 1180 M +0.058 0 (tinytext)A +; : 184 1213 196 32 rc 0 0 0 sco F0_27 +Ji +184 1213 M +-0.074 0 (program)A +; : 400 1213 190 32 rc 0 0 0 sco F0_27 +Ji +400 1213 M +-0.001 0 (VARCHAR$64$)A +; : 184 1246 196 32 rc 0 0 0 sco F0_27 +Ji +184 1246 M +-0.002 0 (initialowner)A +; : 400 1246 190 32 rc 0 0 0 sco F0_27 +Ji +400 1246 M +0.058 0 (tinytext)A +; : 184 1279 196 32 rc 0 0 0 sco F0_27 +Ji +184 1279 M +0.151 0 (initialqacontact)A +; : 400 1279 190 32 rc 0 0 0 sco F0_27 +Ji +400 1279 M +0.058 0 (tinytext)A +; : 184 1312 196 29 rc 0 0 0 sco F0_27 +Ji +184 1312 M +0.132 0 (description)A +; : 400 1312 190 29 rc 0 0 0 sco F0_27 +Ji +400 1312 M +-0.154 0 (mediumtext)A +; +643 1054 N M 320 143 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 665 1059 288 32 rc 0 0 0 sco F0_27 +Ji +738 1059 M +0.097 0 (milestones)A +; : 0 0 2454 3191 rc +643 1094 N M 320 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 653 1097 100 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +653 1097 M +-0.106 0 (value)A +-64 sU +; : 773 1097 190 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +773 1097 M +-0.001 0 (VARCHAR$20$)A +-180 sU +; : 653 1130 100 32 rc 0 0 0 sco F0_27 +Ji +653 1130 M +0.136 0 (product)A +; : 773 1130 190 32 rc 0 0 0 sco F0_27 +Ji +773 1130 M +-0.001 0 (VARCHAR$64$)A +; : 653 1163 100 31 rc 0 0 0 sco F0_27 +Ji +653 1163 M +0.283 0 (sortkey)A +; : 773 1163 190 31 rc 0 0 0 sco F0_27 +Ji +773 1163 M +0.046 0 (smallint$6$)A +; +1742 1001 N M 432 303 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1832 1006 332 32 rc 0 0 0 sco F0_27 +Ji +1905 1006 M +0.182 0 (products)A +; : 0 0 2454 3191 rc +1742 1042 N M 432 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1752 1044 212 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1752 1044 M +0.136 0 (product)A +-91 sU +; : 1984 1044 190 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1984 1044 M +-0.001 0 (VARCHAR$64$)A +-180 sU +; : 1752 1077 212 32 rc 0 0 0 sco F0_27 +Ji +1752 1077 M +0.132 0 (description)A +; : 1984 1077 190 32 rc 0 0 0 sco F0_27 +Ji +1984 1077 M +-0.154 0 (mediumtext)A +; : 1752 1110 212 32 rc 0 0 0 sco F0_27 +Ji +1752 1110 M +0.039 0 (milestoneurl)A +; : 1984 1110 190 32 rc 0 0 0 sco F0_27 +Ji +1984 1110 M +0.058 0 (tinytext)A +; : 1752 1143 212 32 rc 0 0 0 sco F0_27 +Ji +1752 1143 M +-0.048 0 (disallownew)A +; : 1984 1143 190 32 rc 0 0 0 sco F0_27 +Ji +1984 1143 M +0.148 0 (tinyint$4$)A +; : 1752 1176 212 32 rc 0 0 0 sco F0_27 +Ji +1752 1176 M +0.078 0 (votesperuser)A +; : 1984 1176 190 32 rc 0 0 0 sco F0_27 +Ji +1984 1176 M +0.046 0 (smallint$6$)A +; : 1752 1209 212 32 rc 0 0 0 sco F0_27 +Ji +1752 1209 M +-0.113 0 (maxvotesperbug)A +; : 1984 1209 190 32 rc 0 0 0 sco F0_27 +Ji +1984 1209 M +0.046 0 (smallint$6$)A +; : 1752 1242 212 32 rc 0 0 0 sco F0_27 +Ji +1752 1242 M +0.032 0 (votestoconfirm)A +; : 1984 1242 190 32 rc 0 0 0 sco F0_27 +Ji +1984 1242 M +0.046 0 (smallint$6$)A +; : 1752 1275 212 27 rc 0 0 0 sco F0_27 +Ji +1752 1275 M +0.026 0 (defaultmilestone)A +; : 1984 1275 190 27 rc 0 0 0 sco F0_27 +Ji +1984 1275 M +-0.001 0 (VARCHAR$20$)A +; +1052 964 N M 328 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1092 969 278 32 rc 0 0 0 sco F0_27 +Ji +1165 969 M +0.060 0 (versions)A +; : 0 0 2454 3191 rc +1052 1004 N M 328 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1062 1007 108 32 rc 0 0 0 sco F0_27 +Ji +1062 1007 M +-0.106 0 (value)A +; : 1190 1007 190 32 rc 0 0 0 sco F0_27 +Ji +1190 1007 M +0.058 0 (tinytext)A +; : 1062 1040 108 32 rc 0 0 0 sco F0_27 +Ji +1062 1040 M +-0.074 0 (program)A +; : 1190 1040 190 32 rc 0 0 0 sco F0_27 +Ji +1190 1040 M +-0.001 0 (VARCHAR$64$)A +; +1282 1466 N M 382 207 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1358 1471 296 32 rc 0 0 0 sco F0_27 +Ji +1431 1471 M +0.077 0 (groups)A +; : 0 0 2454 3191 rc +1282 1506 N M 382 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1292 1509 147 32 rc 0 0 0 sco F0_27 +Ji +1292 1509 M +0.163 0 (bit)A +; : 1459 1509 205 32 rc 0 0 0 sco F0_27 +Ji +1459 1509 M +0.046 0 (bigint$20$)A +; : 1292 1542 147 32 rc 0 0 0 sco F0_27 +Ji +1292 1542 M +-0.132 0 (name)A +; : 1459 1542 205 32 rc 0 0 0 sco F0_27 +Ji +1459 1542 M +-0.002 0 (VARCHAR$255$)A +; : 1292 1575 147 32 rc 0 0 0 sco F0_27 +Ji +1292 1575 M +0.132 0 (description)A +; : 1459 1575 205 32 rc 0 0 0 sco F0_27 +Ji +1459 1575 M +-0.131 0 (text)A +; : 1292 1608 147 32 rc 0 0 0 sco F0_27 +Ji +1292 1608 M +0.043 0 (isbuggroup)A +; : 1459 1608 205 32 rc 0 0 0 sco F0_27 +Ji +1459 1608 M +0.148 0 (tinyint$4$)A +; : 1292 1641 147 29 rc 0 0 0 sco F0_27 +Ji +1292 1641 M +-0.105 0 (userregexp)A +; : 1459 1641 205 29 rc 0 0 0 sco F0_27 +Ji +1459 1641 M +0.058 0 (tinytext)A +; +671 1361 N M 426 207 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 736 1366 351 32 rc 0 0 0 sco F0_27 +Ji +809 1366 M +0.121 0 (logincookies)A +; : 0 0 2454 3191 rc +671 1401 N M 426 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 681 1404 191 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +681 1404 M +0.162 0 (cookie)A +-79 sU +; : 892 1404 205 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +892 1404 M +-0.043 0 (mediumint$9$)A +-157 sU +; : 681 1437 191 32 rc 0 0 0 sco F0_27 +Ji +681 1437 M +0.080 0 (userid)A +; : 892 1437 205 32 rc 0 0 0 sco F0_27 +Ji +892 1437 M +-0.043 0 (mediumint$9$)A +; : 681 1470 191 32 rc 0 0 0 sco F0_27 +Ji +681 1470 M +0.151 0 (cryptpassword)A +; : 892 1470 205 32 rc 0 0 0 sco F0_27 +Ji +892 1470 M +-0.001 0 (VARCHAR$64$)A +; : 681 1503 191 32 rc 0 0 0 sco F0_27 +Ji +681 1503 M +0.055 0 (hostname)A +; : 892 1503 205 32 rc 0 0 0 sco F0_27 +Ji +892 1503 M +-0.002 0 (VARCHAR$128$)A +; : 681 1536 191 29 rc 0 0 0 sco F0_27 +Ji +681 1536 M +0.182 0 (lastused)A +; : 892 1536 205 29 rc 0 0 0 sco F0_27 +Ji +892 1536 M +0.036 0 (timestamp$14$)A +; +136 1493 N M 382 207 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 168 1498 340 32 rc 0 0 0 sco F0_27 +Ji +241 1498 M +-0.006 0 (namedqueries)A +; : 0 0 2454 3191 rc +136 1533 N M 382 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 146 1536 162 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +146 1536 M +0.080 0 (userid)A +-74 sU +; : 328 1536 190 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +328 1536 M +-0.043 0 (mediumint$9$)A +-157 sU +; : 146 1569 162 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +146 1569 M +-0.132 0 (name)A +-67 sU +; : 328 1569 190 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +328 1569 M +-0.001 0 (VARCHAR$64$)A +-180 sU +; : 146 1602 162 32 rc 0 0 0 sco F0_27 +Ji +146 1602 M +-0.042 0 (watchfordiffs)A +; : 328 1602 190 32 rc 0 0 0 sco F0_27 +Ji +328 1602 M +0.148 0 (tinyint$4$)A +; : 146 1635 162 32 rc 0 0 0 sco F0_27 +Ji +146 1635 M +0.038 0 (linkinfooter)A +; : 328 1635 190 32 rc 0 0 0 sco F0_27 +Ji +328 1635 M +0.148 0 (tinyint$4$)A +; : 146 1668 162 29 rc 0 0 0 sco F0_27 +Ji +146 1668 M +0.095 0 (query)A +; : 328 1668 190 29 rc 0 0 0 sco F0_27 +Ji +328 1668 M +-0.154 0 (mediumtext)A +; +1165 2554 N M 378 335 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1206 2559 327 32 rc 0 0 0 sco F0_27 +Ji +1279 2559 M +0.176 0 (attachments)A +; : 0 0 2454 3191 rc +1165 2595 N M 378 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1175 2597 165 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1175 2597 M +0.159 0 (attach_id)A +-111 sU +; : 1360 2597 183 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1360 2597 M +-0.043 0 (mediumint$9$)A +-157 sU +; : 1175 2630 165 32 rc 0 0 0 sco F0_27 +Ji +1175 2630 M +-0.009 0 (bug_id)A +; : 1360 2630 183 32 rc 0 0 0 sco F0_27 +Ji +1360 2630 M +-0.043 0 (mediumint$9$)A +; : 1175 2663 165 32 rc 0 0 0 sco F0_27 +Ji +1175 2663 M +0.177 0 (creation_ts)A +; : 1360 2663 183 32 rc 0 0 0 sco F0_27 +Ji +1360 2663 M +0.036 0 (timestamp$14$)A +; : 1175 2696 165 32 rc 0 0 0 sco F0_27 +Ji +1175 2696 M +0.132 0 (description)A +; : 1360 2696 183 32 rc 0 0 0 sco F0_27 +Ji +1360 2696 M +-0.154 0 (mediumtext)A +; : 1175 2729 165 32 rc 0 0 0 sco F0_27 +Ji +1175 2729 M +-0.002 0 (mimetype)A +; : 1360 2729 183 32 rc 0 0 0 sco F0_27 +Ji +1360 2729 M +-0.154 0 (mediumtext)A +; : 1175 2762 165 32 rc 0 0 0 sco F0_27 +Ji +1175 2762 M +0.209 0 (ispatch)A +; : 1360 2762 183 32 rc 0 0 0 sco F0_27 +Ji +1360 2762 M +0.148 0 (tinyint$4$)A +; : 1175 2795 165 32 rc 0 0 0 sco F0_27 +Ji +1175 2795 M +-0.129 0 (filename)A +; : 1360 2795 183 32 rc 0 0 0 sco F0_27 +Ji +1360 2795 M +-0.154 0 (mediumtext)A +; : 1175 2828 165 32 rc 0 0 0 sco F0_27 +Ji +1175 2828 M +0.133 0 (thedata)A +; : 1360 2828 183 32 rc 0 0 0 sco F0_27 +Ji +1360 2828 M +-0.007 0 (longblob)A +; : 1175 2861 165 26 rc 0 0 0 sco F0_27 +Ji +1175 2861 M +0.080 0 (submitter_id)A +; : 1360 2861 183 26 rc 0 0 0 sco F0_27 +Ji +1360 2861 M +-0.043 0 (mediumint$9$)A +; +1826 2227 N M 456 815 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1951 2232 321 32 rc 0 0 0 sco F0_27 +Ji +2024 2232 M +0.116 0 (bugs)A +; : 0 0 2454 3191 rc +1826 2268 N M 456 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1836 2270 236 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1836 2270 M +-0.009 0 (bug_id)A +-81 sU +; : 2092 2270 190 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +2092 2270 M +-0.043 0 (mediumint$9$)A +-157 sU +; : 1836 2303 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2303 M +0.118 0 (groupset)A +; : 2092 2303 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2303 M +0.046 0 (bigint$20$)A +; : 1836 2336 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2336 M +0.129 0 (assigned_to)A +; : 2092 2336 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2336 M +-0.043 0 (mediumint$9$)A +; : 1836 2369 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2369 M +-0.006 0 (bug_file_loc)A +; : 2092 2369 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2369 M +-0.131 0 (text)A +; : 1836 2402 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2402 M +0.078 0 (bug_severity)A +; : 2092 2402 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2402 M +-0.132 0 (enum)A +; : 1836 2435 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2435 M +0.192 0 (bug_status)A +; : 2092 2435 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2435 M +-0.132 0 (enum)A +; : 1836 2468 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2468 M +0.177 0 (creation_ts)A +; : 2092 2468 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2468 M +0.057 0 (datetime)A +; : 1836 2501 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2501 M +0.181 0 (delta_ts)A +; : 2092 2501 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2501 M +0.036 0 (timestamp$14$)A +; : 1836 2534 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2534 M +0.194 0 (short_desc)A +; : 2092 2534 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2534 M +-0.154 0 (mediumtext)A +; : 1836 2567 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2567 M +0.244 0 (op_sys)A +; : 2092 2567 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2567 M +-0.132 0 (enum)A +; : 1836 2600 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2600 M +0.125 0 (priority)A +; : 2092 2600 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2600 M +-0.132 0 (enum)A +; : 1836 2633 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2633 M +0.136 0 (product)A +; : 2092 2633 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2633 M +-0.001 0 (VARCHAR$64$)A +; : 1836 2666 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2666 M +-0.046 0 (rep_platform)A +; : 2092 2666 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2666 M +-0.132 0 (enum)A +; : 1836 2699 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2699 M +0.059 0 (reporter)A +; : 2092 2699 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2699 M +-0.043 0 (mediumint$9$)A +; : 1836 2732 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2732 M +-0.003 0 (version)A +; : 2092 2732 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2732 M +-0.001 0 (VARCHAR$16$)A +; : 1836 2765 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2765 M +0.048 0 (component)A +; : 2092 2765 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2765 M +-0.001 0 (VARCHAR$50$)A +; : 1836 2798 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2798 M +0.096 0 (resolution)A +; : 2092 2798 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2798 M +-0.132 0 (enum)A +; : 1836 2831 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2831 M +0.089 0 (target_milestone)A +; : 2092 2831 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2831 M +-0.001 0 (VARCHAR$20$)A +; : 1836 2864 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2864 M +0.192 0 (qa_contact)A +; : 2092 2864 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2864 M +-0.043 0 (mediumint$9$)A +; : 1836 2897 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2897 M +0.111 0 (status_whiteboard)A +; : 2092 2897 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2897 M +-0.154 0 (mediumtext)A +; : 1836 2930 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2930 M +0.094 0 (votes)A +; : 2092 2930 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2930 M +-0.043 0 (mediumint$9$)A +; : 1836 2963 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2963 M +0.122 0 (keywords)A +; : 2092 2963 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2963 M +-0.154 0 (mediumtext)A +; : 1836 2996 236 32 rc 0 0 0 sco F0_27 +Ji +1836 2996 M +-0.005 0 (lastdiffed)A +; : 2092 2996 190 32 rc 0 0 0 sco F0_27 +Ji +2092 2996 M +0.057 0 (datetime)A +; : 1836 3029 236 11 rc 0 0 0 sco F0_27 +Ji +1836 3029 M +-0.080 0 (everconfirmed)A +; : 2092 3029 190 11 rc 0 0 0 sco F0_27 +Ji +2092 3029 M +0.148 0 (tinyint$4$)A +; +768 2778 N M 330 239 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 781 2783 307 32 rc 0 0 0 sco F0_27 +Ji +854 2783 M +0.149 0 (bugs_activity)A +; : 0 0 2454 3191 rc +768 2819 N M 330 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 778 2821 133 32 rc 0 0 0 sco F0_27 +Ji +778 2821 M +-0.009 0 (bug_id)A +; : 931 2821 167 32 rc 0 0 0 sco F0_27 +Ji +931 2821 M +-0.043 0 (mediumint$9$)A +; : 778 2854 133 32 rc 0 0 0 sco F0_27 +Ji +778 2854 M +-0.173 0 (who)A +; : 931 2854 167 32 rc 0 0 0 sco F0_27 +Ji +931 2854 M +-0.043 0 (mediumint$9$)A +; : 778 2887 133 32 rc 0 0 0 sco F0_27 +Ji +778 2887 M +-0.072 0 (bug_when)A +; : 931 2887 167 32 rc 0 0 0 sco F0_27 +Ji +931 2887 M +0.057 0 (datetime)A +; : 778 2920 133 32 rc 0 0 0 sco F0_27 +Ji +778 2920 M +-0.075 0 (fieldid)A +; : 931 2920 167 32 rc 0 0 0 sco F0_27 +Ji +931 2920 M +-0.043 0 (mediumint$9$)A +; : 778 2953 133 32 rc 0 0 0 sco F0_27 +Ji +778 2953 M +-0.069 0 (oldvalue)A +; : 931 2953 167 32 rc 0 0 0 sco F0_27 +Ji +931 2953 M +0.058 0 (tinytext)A +; : 778 2986 133 29 rc 0 0 0 sco F0_27 +Ji +778 2986 M +-0.131 0 (newvalue)A +; : 931 2986 167 29 rc 0 0 0 sco F0_27 +Ji +931 2986 M +0.058 0 (tinytext)A +; +1370 1784 N M 286 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1426 1789 220 32 rc 0 0 0 sco F0_27 +Ji +1499 1789 M +0.500 0 (cc)A +; : 0 0 2454 3191 rc +1370 1825 N M 286 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1380 1827 89 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1380 1827 M +-0.009 0 (bug_id)A +-81 sU +; : 1489 1827 167 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1489 1827 M +-0.043 0 (mediumint$9$)A +-157 sU +; : 1380 1860 89 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1380 1860 M +-0.173 0 (who)A +-49 sU +; : 1489 1860 167 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1489 1860 M +-0.043 0 (mediumint$9$)A +-157 sU +; +178 2819 N M 364 207 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 237 2824 295 32 rc 0 0 0 sco F0_27 +Ji +310 2824 M +-0.061 0 (fielddefs)A +; : 0 0 2454 3191 rc +178 2859 N M 364 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 188 2862 144 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +188 2862 M +-0.075 0 (fieldid)A +-70 sU +; : 352 2862 190 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +352 2862 M +-0.043 0 (mediumint$9$)A +-157 sU +; : 188 2895 144 32 rc 0 0 0 sco F0_27 +Ji +188 2895 M +-0.132 0 (name)A +; : 352 2895 190 32 rc 0 0 0 sco F0_27 +Ji +352 2895 M +-0.001 0 (VARCHAR$64$)A +; : 188 2928 144 32 rc 0 0 0 sco F0_27 +Ji +188 2928 M +0.132 0 (description)A +; : 352 2928 190 32 rc 0 0 0 sco F0_27 +Ji +352 2928 M +-0.154 0 (mediumtext)A +; : 188 2961 144 32 rc 0 0 0 sco F0_27 +Ji +188 2961 M +-0.067 0 (mailhead)A +; : 352 2961 190 32 rc 0 0 0 sco F0_27 +Ji +352 2961 M +0.148 0 (tinyint$4$)A +; : 188 2994 144 29 rc 0 0 0 sco F0_27 +Ji +188 2994 M +0.283 0 (sortkey)A +; : 352 2994 190 29 rc 0 0 0 sco F0_27 +Ji +352 2994 M +0.046 0 (smallint$6$)A +; +1954 1803 N M 330 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1988 1808 286 32 rc 0 0 0 sco F0_27 +Ji +2061 1808 M +0.122 0 (keywords)A +; : 0 0 2454 3191 rc +1954 1843 N M 330 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1964 1846 133 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1964 1846 M +-0.009 0 (bug_id)A +-81 sU +; : 2117 1846 167 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +2117 1846 M +-0.043 0 (mediumint$9$)A +-157 sU +; : 1964 1879 133 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1964 1879 M +0.053 0 (keywordid)A +-122 sU +; : 2117 1879 167 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +2117 1879 M +0.046 0 (smallint$6$)A +-125 sU +; +1104 2179 N M 330 175 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1134 2184 290 32 rc 0 0 0 sco F0_27 +Ji +1207 2184 M +0.161 0 (longdescs)A +; : 0 0 2454 3191 rc +1104 2220 N M 330 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1114 2222 133 32 rc 0 0 0 sco F0_27 +Ji +1114 2222 M +-0.009 0 (bug_id)A +; : 1267 2222 167 32 rc 0 0 0 sco F0_27 +Ji +1267 2222 M +-0.043 0 (mediumint$9$)A +; : 1114 2255 133 32 rc 0 0 0 sco F0_27 +Ji +1114 2255 M +-0.173 0 (who)A +; : 1267 2255 167 32 rc 0 0 0 sco F0_27 +Ji +1267 2255 M +-0.043 0 (mediumint$9$)A +; : 1114 2288 133 32 rc 0 0 0 sco F0_27 +Ji +1114 2288 M +-0.072 0 (bug_when)A +; : 1267 2288 167 32 rc 0 0 0 sco F0_27 +Ji +1267 2288 M +0.057 0 (datetime)A +; : 1114 2321 133 31 rc 0 0 0 sco F0_27 +Ji +1114 2321 M +-0.008 0 (thetext)A +; : 1267 2321 167 31 rc 0 0 0 sco F0_27 +Ji +1267 2321 M +-0.154 0 (mediumtext)A +; +426 2221 N M 446 399 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 532 2226 330 32 rc 0 0 0 sco F0_27 +Ji +605 2226 M +-0.003 0 (profiles)A +; : 0 0 2454 3191 rc +426 2262 N M 446 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 436 2264 211 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +436 2264 M +0.080 0 (userid)A +-74 sU +; : 667 2264 205 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +667 2264 M +-0.043 0 (mediumint$9$)A +-157 sU +; : 436 2297 211 32 rc 0 0 0 sco F0_27 +Ji +436 2297 M +-0.056 0 (login_name)A +; : 667 2297 205 32 rc 0 0 0 sco F0_27 +Ji +667 2297 M +-0.002 0 (VARCHAR$255$)A +; : 436 2330 211 32 rc 0 0 0 sco F0_27 +Ji +436 2330 M +0.058 0 (password)A +; : 667 2330 205 32 rc 0 0 0 sco F0_27 +Ji +667 2330 M +-0.001 0 (VARCHAR$16$)A +; : 436 2363 211 32 rc 0 0 0 sco F0_27 +Ji +436 2363 M +0.151 0 (cryptpassword)A +; : 667 2363 205 32 rc 0 0 0 sco F0_27 +Ji +667 2363 M +-0.001 0 (VARCHAR$64$)A +; : 436 2396 211 32 rc 0 0 0 sco F0_27 +Ji +436 2396 M +-0.067 0 (realname)A +; : 667 2396 205 32 rc 0 0 0 sco F0_27 +Ji +667 2396 M +-0.002 0 (VARCHAR$255$)A +; : 436 2429 211 32 rc 0 0 0 sco F0_27 +Ji +436 2429 M +0.118 0 (groupset)A +; : 667 2429 205 32 rc 0 0 0 sco F0_27 +Ji +667 2429 M +0.046 0 (bigint$20$)A +; : 436 2462 211 32 rc 0 0 0 sco F0_27 +Ji +436 2462 M +0.026 0 (emailnotification)A +; : 667 2462 205 32 rc 0 0 0 sco F0_27 +Ji +667 2462 M +-0.132 0 (enum)A +; : 436 2495 211 32 rc 0 0 0 sco F0_27 +Ji +436 2495 M +-0.006 0 (disabledtext)A +; : 667 2495 205 32 rc 0 0 0 sco F0_27 +Ji +667 2495 M +-0.154 0 (mediumtext)A +; : 436 2528 211 32 rc 0 0 0 sco F0_27 +Ji +436 2528 M +-0.004 0 (newemailtech)A +; : 667 2528 205 32 rc 0 0 0 sco F0_27 +Ji +667 2528 M +0.148 0 (tinyint$4$)A +; : 436 2561 211 32 rc 0 0 0 sco F0_27 +Ji +436 2561 M +0.097 0 (mybugslink)A +; : 667 2561 205 32 rc 0 0 0 sco F0_27 +Ji +667 2561 M +0.148 0 (tinyint$4$)A +; : 436 2594 211 24 rc 0 0 0 sco F0_27 +Ji +436 2594 M +0.148 0 (blessgroupset)A +; : 667 2594 205 24 rc 0 0 0 sco F0_27 +Ji +667 2594 M +0.046 0 (bigint$20$)A +; +150 1818 N M 374 239 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 171 1823 343 32 rc 0 0 0 sco F0_27 +Ji +244 1823 M +0.086 0 (profiles_activity)A +; : 0 0 2454 3191 rc +150 1858 N M 374 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 160 1861 177 32 rc 0 0 0 sco F0_27 +Ji +160 1861 M +0.080 0 (userid)A +; : 357 1861 167 32 rc 0 0 0 sco F0_27 +Ji +357 1861 M +-0.043 0 (mediumint$9$)A +; : 160 1894 177 32 rc 0 0 0 sco F0_27 +Ji +160 1894 M +-0.173 0 (who)A +; : 357 1894 167 32 rc 0 0 0 sco F0_27 +Ji +357 1894 M +-0.043 0 (mediumint$9$)A +; : 160 1927 177 32 rc 0 0 0 sco F0_27 +Ji +160 1927 M +-0.043 0 (profiles_when)A +; : 357 1927 167 32 rc 0 0 0 sco F0_27 +Ji +357 1927 M +0.057 0 (datetime)A +; : 160 1960 177 32 rc 0 0 0 sco F0_27 +Ji +160 1960 M +-0.075 0 (fieldid)A +; : 357 1960 167 32 rc 0 0 0 sco F0_27 +Ji +357 1960 M +-0.043 0 (mediumint$9$)A +; : 160 1993 177 32 rc 0 0 0 sco F0_27 +Ji +160 1993 M +-0.069 0 (oldvalue)A +; : 357 1993 167 32 rc 0 0 0 sco F0_27 +Ji +357 1993 M +0.058 0 (tinytext)A +; : 160 2026 177 28 rc 0 0 0 sco F0_27 +Ji +160 2026 M +-0.131 0 (newvalue)A +; : 357 2026 167 28 rc 0 0 0 sco F0_27 +Ji +357 2026 M +0.058 0 (tinytext)A +; +1289 1975 N M 286 143 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1326 1980 239 32 rc 0 0 0 sco F0_27 +Ji +1399 1980 M +0.094 0 (votes)A +; : 0 0 2454 3191 rc +1289 2016 N M 286 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1299 2018 89 32 rc 0 0 0 sco F0_27 +Ji +1299 2018 M +-0.173 0 (who)A +; : 1408 2018 167 32 rc 0 0 0 sco F0_27 +Ji +1408 2018 M +-0.043 0 (mediumint$9$)A +; : 1299 2051 89 32 rc 0 0 0 sco F0_27 +Ji +1299 2051 M +-0.009 0 (bug_id)A +; : 1408 2051 167 32 rc 0 0 0 sco F0_27 +Ji +1408 2051 M +-0.043 0 (mediumint$9$)A +; : 1299 2084 89 32 rc 0 0 0 sco F0_27 +Ji +1299 2084 M +0.192 0 (count)A +; : 1408 2084 167 32 rc 0 0 0 sco F0_27 +Ji +1408 2084 M +0.046 0 (smallint$6$)A +; +1914 755 N M 342 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1927 760 319 32 rc 0 0 0 sco F0_27 +Ji +2000 760 M +0.075 0 (dependencies)A +; : 0 0 2454 3191 rc +1914 796 N M 342 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1924 798 145 32 rc 0 0 0 sco F0_27 +Ji +1924 798 M +0.137 0 (blocked)A +; : 2089 798 167 32 rc 0 0 0 sco F0_27 +Ji +2089 798 M +-0.043 0 (mediumint$9$)A +; : 1924 831 145 32 rc 0 0 0 sco F0_27 +Ji +1924 831 M +0.045 0 (dependson)A +; : 2089 831 167 32 rc 0 0 0 sco F0_27 +Ji +2089 831 M +-0.043 0 (mediumint$9$)A +; +1548 755 N M 302 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1564 760 276 32 rc 0 0 0 sco F0_27 +Ji +1637 760 M +0.145 0 (duplicates)A +; : 0 0 2454 3191 rc +1548 796 N M 302 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1558 798 105 32 rc 0 0 0 sco F0_27 +Ji +1558 798 M +-0.083 0 (dupe_of)A +; : 1683 798 167 32 rc 0 0 0 sco F0_27 +Ji +1683 798 M +-0.043 0 (mediumint$9$)A +; : 1558 831 105 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1558 831 M +-0.012 0 (dupe)A +-60 sU +; : 1683 831 167 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1683 831 M +-0.043 0 (mediumint$9$)A +-157 sU +; +1058 728 N M 364 143 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1091 733 321 32 rc 0 0 0 sco F0_27 +Ji +1164 733 M +0.041 0 (keyworddefs)A +; : 0 0 2454 3191 rc +1058 769 N M 364 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1068 771 144 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1068 771 M +-0.003 0 (id)A +-21 sU +; : 1232 771 190 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +1232 771 M +0.046 0 (smallint$6$)A +-125 sU +; : 1068 804 144 32 rc 0 0 0 sco F0_27 +Ji +1068 804 M +-0.132 0 (name)A +; : 1232 804 190 32 rc 0 0 0 sco F0_27 +Ji +1232 804 M +-0.001 0 (VARCHAR$64$)A +; : 1068 837 144 32 rc 0 0 0 sco F0_27 +Ji +1068 837 M +0.132 0 (description)A +; : 1232 837 190 32 rc 0 0 0 sco F0_27 +Ji +1232 837 M +-0.154 0 (mediumtext)A +; +170 696 N M 346 175 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 205 701 301 32 rc 0 0 0 sco F0_27 +Ji +278 701 M +-0.007 0 (shadowlog)A +; : 0 0 2454 3191 rc +170 737 N M 346 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 180 739 133 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +180 739 M +-0.003 0 (id)A +-21 sU +; : 333 739 183 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +333 739 M +0.069 0 (int$11$)A +-77 sU +; : 180 772 133 32 rc 0 0 0 sco F0_27 +Ji +180 772 M +0.497 0 (ts)A +; : 333 772 183 32 rc 0 0 0 sco F0_27 +Ji +333 772 M +0.036 0 (timestamp$14$)A +; : 180 805 133 32 rc 0 0 0 sco F0_27 +Ji +180 805 M +0.051 0 (reflected)A +; : 333 805 183 32 rc 0 0 0 sco F0_27 +Ji +333 805 M +0.148 0 (tinyint$4$)A +; : 180 838 133 31 rc 0 0 0 sco F0_27 +Ji +180 838 M +-0.076 0 (command)A +; : 333 838 183 31 rc 0 0 0 sco F0_27 +Ji +333 838 M +-0.154 0 (mediumtext)A +; +646 755 N M 308 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 691 760 253 32 rc 0 0 0 sco F0_27 +Ji +764 760 M +0.095 0 (watch)A +; : 0 0 2454 3191 rc +646 796 N M 308 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 656 798 111 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +656 798 M +0.068 0 (watcher)A +-95 sU +; : 787 798 167 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +787 798 M +-0.043 0 (mediumint$9$)A +-157 sU +; : 656 831 111 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +656 831 M +0.065 0 (watched)A +-101 sU +; : 787 831 167 32 rc 0 0 0 sco F0_27 +Ji +0 29 1 sSU +787 831 M +-0.043 0 (mediumint$9$)A +-157 sU +; : 0 0 2454 3191 rc +780 2186 N M -3 -403 - 459 -177 - 1 Lc 1 Lj [ 37 25 ] setdsh : 1.000 1.000 1.000 sco solid K ; 0 0 0 sco K ; : 0 0 2454 3191 rc +1686 1620 N M 160 243 - 0 331 - 1 Lc 1 Lj [ 37 25 ] setdsh : 1.000 1.000 1.000 sco solid K ; 0 0 0 sco K ; +LH +pagesave restore + +(%%[ Page: 1 ]%%) = +%%PageTrailer + +%%Trailer +%%DocumentNeededFonts: Helvetica +%%DocumentSuppliedFonts: +Pscript_Win_Driver_Incr dup /terminate get exec +savelevel0 restore +%%Pages: 1 +(%%[ LastPage ]%%) = +%%EOF +%-12345X@PJL EOJ +%-12345X \ No newline at end of file diff --git a/docs/sgml/Bugzilla-Guide.sgml b/docs/sgml/Bugzilla-Guide.sgml index 59befaf0a..8f2136bd8 100644 --- a/docs/sgml/Bugzilla-Guide.sgml +++ b/docs/sgml/Bugzilla-Guide.sgml @@ -26,7 +26,7 @@ -barnboy@NOSPAM.trilobyte.net"> +barnboy@trilobyte.net"> @@ -126,14 +126,14 @@ try to avoid clutter and feel free to waste space in the code to make it more re P. Barnson -
barnboy@NOSPAM.trilobyte.net
+
barnboy@trilobyte.net
Zach Lipton -
zach@NOSPAM.zachlipton.com
+
zach AT zachlipton DOT com
@@ -196,6 +196,9 @@ try to avoid clutter and feel free to waste space in the code to make it more re &future; + +&variants; + &faq; @@ -205,9 +208,6 @@ try to avoid clutter and feel free to waste space in the code to make it more re &database; - -&variants; - &patches; diff --git a/docs/sgml/about.sgml b/docs/sgml/about.sgml index 89f7bb127..04e054bc2 100644 --- a/docs/sgml/about.sgml +++ b/docs/sgml/about.sgml @@ -70,8 +70,7 @@ If you have any questions regarding this document, its copyright, or publishing this document in non-electronic form, - please contact &bzg-auth;. Remove "NOSPAM" from email address - to send. + please contact &bzg-auth;. @@ -172,8 +171,8 @@ Terry Weissman - for initially converting Bugzilla from BugSplat! and writing the - README upon which this documentation is largely based. + for initially writing Bugzilla and creating the + README upon which the UNIX installation documentation is largely based. Tara @@ -204,7 +203,8 @@ documentation (in no particular order): - Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron Teitelbaum + Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron + Teitelbaum, Jacob Steenhagen, Joe Robins
diff --git a/docs/sgml/administration.sgml b/docs/sgml/administration.sgml index 54f984fbc..98e726312 100644 --- a/docs/sgml/administration.sgml +++ b/docs/sgml/administration.sgml @@ -1192,6 +1192,103 @@ + + You may find this example illustrative for how bug groups work. + + Bugzilla Groups + +Bugzilla Groups example +----------------------- + +For this example, let us suppose we have four groups, call them +Group1, Group2, Group3, and Group4. + +We have 5 users, User1, User2, User3, User4, User5. + +We have 8 bugs, Bug1, ..., Bug8. + +Group membership is defined by this chart: +(X denotes that user is in that group.) +(I apologize for the nasty formatting of this table. Try viewing +it in a text-based browser or something for now. -MPB) + + G G G G + r r r r + o o o o + u u u u + p p p p + 1 2 3 4 + +-+-+-+-+ +User1|X| | | | + +-+-+-+-+ +User2| |X| | | + +-+-+-+-+ +User3|X| |X| | + +-+-+-+-+ +User4|X|X|X| | + +-+-+-+-+ +User5| | | | | + +-+-+-+-+ + +Bug restrictions are defined by this chart: +(X denotes that bug is restricted to that group.) + + G G G G + r r r r + o o o o + u u u u + p p p p + 1 2 3 4 + +-+-+-+-+ +Bug1| | | | | + +-+-+-+-+ +Bug2| |X| | | + +-+-+-+-+ +Bug3| | |X| | + +-+-+-+-+ +Bug4| | | |X| + +-+-+-+-+ +Bug5|X|X| | | + +-+-+-+-+ +Bug6|X| |X| | + +-+-+-+-+ +Bug7|X|X|X| | + +-+-+-+-+ +Bug8|X|X|X|X| + +-+-+-+-+ + +Who can see each bug? + +Bug1 has no group restrictions. Therefore, Bug1 can be seen by any +user, whatever their group membership. This is going to be the only +bug that User5 can see, because User5 isn't in any groups. + +Bug2 can be seen by anyone in Group2, that is User2 and User4. + +Bug3 can be seen by anyone in Group3, that is User3 and User4. + +Bug4 can be seen by anyone in Group4. Nobody is in Group4, so none of +these users can see Bug4. + +Bug5 can be seen by anyone who is in _both_ Group1 and Group2. This +is only User4. User1 cannot see it because he is not in Group2, and +User2 cannot see it because she is not in Group1. + +Bug6 can be seen by anyone who is in both Group1 and Group3. This +would include User3 and User4. Similar to Bug5, User1 cannot see Bug6 +because he is not in Group3. + +Bug7 can be seen by anyone who is in Group1, Group2, and Group3. This +is only User4. All of the others are missing at least one of those +group priveleges, and thus cannot see the bug. + +Bug8 can be seen by anyone who is in Group1, Group2, Group3, and +Group4. There is nobody in all four of these groups, so nobody can +see Bug8. It doesn't matter that User4 is in Group1, Group2, and +Group3, since he isn't in Group4. + + +
diff --git a/docs/sgml/database.sgml b/docs/sgml/database.sgml index aee9b37e5..7ff52134c 100644 --- a/docs/sgml/database.sgml +++ b/docs/sgml/database.sgml @@ -13,7 +13,7 @@ - + diff --git a/docs/sgml/dbschema.jpg b/docs/sgml/dbschema.jpg deleted file mode 100644 index 17e2422e5..000000000 Binary files a/docs/sgml/dbschema.jpg and /dev/null differ diff --git a/docs/sgml/dbschema.ps b/docs/sgml/dbschema.ps deleted file mode 100644 index 8952a6834..000000000 --- a/docs/sgml/dbschema.ps +++ /dev/null @@ -1,1733 +0,0 @@ -%-12345X@PJL JOB -@PJL ENTER LANGUAGE = POSTSCRIPT - -%!PS-Adobe-3.0 -%%Title: PDM Model_7 - I:\DATA\SDESI -%%Creator: PSCRIPT.DRV Version 4.0 -%%CreationDate: 12/06/00 23:59:39 -%%BoundingBox: 12 13 601 779 -%%Pages: (atend) -%%PageOrder: Special -%%Requirements: -%%DocumentNeededFonts: (atend) -%%DocumentSuppliedFonts: (atend) -%%DocumentData: Clean7Bit -%%LanguageLevel: 2 -%%EndComments - -%%BeginProlog -%%BeginProcSet: Pscript_Win_ErrorHandler 1.0 1 -/currentpacking where{pop/oldpack currentpacking def/setpacking where{pop -false setpacking}if}if/$brkpage 64 dict def $brkpage begin/prnt{dup type -/stringtype ne{=string cvs}if dup length 6 mul/tx exch def/ty 10 def -currentpoint/toy exch def/tox exch def 1 setgray newpath tox toy 2 sub moveto -0 ty rlineto tx 0 rlineto 0 ty neg rlineto closepath fill tox toy moveto 0 -setgray show}bind def/nl{currentpoint exch pop lmargin exch moveto 0 -10 -rmoveto}def/=={/cp 0 def typeprint nl}def/typeprint{dup type exec}readonly def -/lmargin 72 def/rmargin 72 def/tprint{dup length cp add rmargin gt{nl/cp 0 def -}if dup length cp add/cp exch def prnt}readonly def/cvsprint{=string cvs -tprint( )tprint}readonly def/integertype{cvsprint}readonly def/realtype{ -cvsprint}readonly def/booleantype{cvsprint}readonly def/operatortype{(--) -tprint =string cvs tprint(-- )tprint}readonly def/marktype{pop(-mark- )tprint} -readonly def/dicttype{pop(-dictionary- )tprint}readonly def/nulltype{pop -(-null- )tprint}readonly def/filetype{pop(-filestream- )tprint}readonly def -/savetype{pop(-savelevel- )tprint}readonly def/fonttype{pop(-fontid- )tprint} -readonly def/nametype{dup xcheck not{(/)tprint}if cvsprint}readonly def -/stringtype{dup rcheck{($)tprint tprint($)tprint}{pop(-string- )tprint} -ifelse}readonly def/arraytype{dup rcheck{dup xcheck{({)tprint{typeprint}forall -(})tprint}{([)tprint{typeprint}forall(])tprint}ifelse}{pop(-array- )tprint} -ifelse}readonly def/packedarraytype{dup rcheck{dup xcheck{({)tprint{typeprint} -forall(})tprint}{([)tprint{typeprint}forall(])tprint}ifelse}{pop -(-packedarray- )tprint}ifelse}readonly def/courier/Courier findfont 10 -scalefont def end errordict/handleerror{systemdict begin $error begin $brkpage -begin newerror{/newerror false store vmstatus pop pop 0 ne{grestoreall}if -showpage initgraphics courier setfont lmargin 720 moveto(ERROR: )prnt -errorname prnt nl(OFFENDING COMMAND: )prnt/command load prnt $error/ostack -known{nl nl(STACK:)prnt nl nl $error/ostack get aload length{==}repeat}if -systemdict/showpage get exec(%%[ Error: )print errorname =print -(; OffendingCommand: )print/command load =print( ]%%)= flush}if end end end} -dup 0 systemdict put dup 4 $brkpage put bind readonly put/currentpacking where -{pop/setpacking where{pop oldpack setpacking}if}if -%%EndProcSet -userdict /Pscript_Win_Driver_Incr 200 dict dup begin put -%%BeginResource: file Pscript_FatalError 2.0 0 -/FatalErrorIf{{initgraphics findfont exch scalefont setfont counttomark 3 div -cvi{moveto show}repeat showpage quit}{cleartomark}ifelse}bind def -%%EndResource -/VM? {vmstatus exch sub exch pop gt { [ -(This job requires more memory than is available in this printer.) 100 500 -(Try one or more of the following, and then print again:) 100 485 -(In the PostScript dialog box, click Optimize For Portability.) 115 470 -(In the Device Options dialog box, make sure the Available Printer Memory is accurate.) 115 455 -(Reduce the number of fonts in the document.) 115 440 -(Print the document in parts.) 115 425 -12 /Times-Roman showpage -(%%[ PrinterError: Low Printer VM ]%%) = -true FatalErrorIf}if} bind def -30000 VM? -%%BeginResource: file Pscript_Win_Utils 2.0 0 -/|/def load def/,/load load |/~/exch , |/?/ifelse , |/!/pop , |/`/begin , |/^ -/index , |/@/dup , |/+/translate , |/$/roll , |/U/userdict , |/M/moveto , |/- -/rlineto , |/&/currentdict , |/:/gsave , |/;/grestore , |/F/false , |/T/true , -|/N/newpath , |/E/end , |/Ac/arc , |/An/arcn , |/A/ashow , |/D/awidthshow , | -/C/closepath , |/V/div , |/O/eofill , |/L/fill , |/I/lineto , |/-C/rcurveto , -|/-M/rmoveto , |/+S/scale , |/Ji/setfont , |/Lc/setlinecap , |/Lj/setlinejoin -, |/Lw/setlinewidth , |/S/show , |/LH/showpage , |/K/stroke , |/W/widthshow , -|/R/rotate , |/b{bind |}bind |/bd{bind |}bind |/xd{~ |}bd/ld{, |}bd/lw/Lw ld -/lc/Lc ld/lj/Lj ld/sg/setgray ld/L2? F/languagelevel where{! languagelevel 2 -ge{! T}if}if |/g{@ not{U/DefIf_save save put}if U/DefIf_bool 2 ^ put}b -/DefIf_El{if U/DefIf_bool get not @{U/DefIf_save get restore}if}b/e{DefIf_El ! -}b/self & |/reinitialize{[/TextInit/GraphInit/UtilsInit counttomark{@ where{ -self eq}{F}?{cvx exec}{!}?}repeat cleartomark}b/initialize{`{/ADO_mxRot ~ | -/TextInitialised? F | reinitialize E}{U/Pscript_Win_Data 200 dict @ ` put -/ADO_mxRot ~ |/TextInitialised? F | reinitialize}?}b/terminate{!{& self eq{ -exit}{E}?}loop E}b/suspend/terminate , |/resume{` Pscript_Win_Data `}b/snap{ -transform 0.25 sub round 0.25 add ~ 0.25 sub round 0.25 add ~ itransform}b -/dsnap{dtransform round ~ round ~ idtransform}b<04>cvn{}|/setjn{{statusdict -/jobname known{statusdict/jobname 3 -1 $ put}if}stopped cleartomark}b/solid{[] -0 setdash}b/setdsh{0 setdash}b/colspRefresh{}b/rp{4 2 $ M 1 ^ 0 - 0 ~ - neg 0 --}b/rr{1 ^ 0 - 0 ~ - neg 0 - C}b -%%EndResource -%%BeginResource: file Pscript_Win_Utils_L1 2.0 0 -L2? not g{/rf{N rp L}b/fx{1 1 dtransform @ 0 ge{1 sub 1}{1 add -0.25}? 3 -1 $ -@ 0 ge{1 sub 1}{1 add -0.25}? 3 1 $ 4 1 $ idtransform 4 -2 $ idtransform}b/BZ{ -4 -2 $ snap + +S fx rf}b/rs{N rp C K}b/rc{N rp clip N}b/sg{setgray}b/sco{ -setrgbcolor}b/sgco{{sg}{sco}?}b}e -%%EndResource -%%BeginResource: file Pscript_Win_Utils_L2 2.0 0 -L2? g{/colspA/DeviceGray |/colspABC/DeviceRGB |/setAorABC{{colspA}{colspABC}? -setcolorspace}b/rf/rectfill , |/fx{1 1 dtransform @ 0 ge{1 sub 0.5}{1 add -0.5 -}? 3 -1 $ @ 0 ge{1 sub 0.5}{1 add -0.5}? 3 1 $ 4 1 $ idtransform 4 -2 $ -idtransform}b/BZ{4 -2 $ snap + +S fx rf}b/rs/rectstroke , |/rc/rectclip , |/sg -{@ @ setcolor}b/sco{setcolor}b/colspRefresh{colspABC setcolorspace}b/sgco{{sg -}{sco}?}b/UtilsInit{F setglobal}b/definecolorrendering{/ColorRendering -defineresource !}b/findcolorrendering{@/ColorRendering resourcestatus{! ! -/ColorRendering findresource T}{! F}?}b/selectcolorrendering{@/ColorRendering -resourcestatus{! !/ColorRendering}{!/DefaultColorRendering/ColorRendering}? -findresource setcolorrendering}b}e -%%EndResource -end -%%EndProlog - -%%BeginSetup -[ 1.000 0 0 1.000 0 0 ] false Pscript_Win_Driver_Incr dup /initialize get exec - -[{0 -/languagelevel where{pop languagelevel}{1}ifelse 2 ge{1 dict dup/JobTimeout 4 -1 roll put setuserparams}{statusdict/setjobtimeout get exec}ifelse -} stopped cleartomark -[{240 -/languagelevel where{pop languagelevel}{1}ifelse 2 ge{1 dict dup/WaitTimeout 4 -1 roll put setuserparams}{statusdict/waittimeout 3 -1 roll put}ifelse -} stopped cleartomark -[{ -%%BeginFeature: *Print as Grayscale No - - <> setpagedevice -%%EndFeature -} stopped cleartomark -[{ - -} stopped cleartomark -[{ -%%BeginFeature: *InputSlot AutoSelect Tray - -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *PageSize Letter - - <> setpagedevice - 2 dict dup /PageSize [612 792] put dup /ImagingBBox null put setpagedevice -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *ColorSmart Text Vivid Color - - globaldict /ColorSmartColorMatching known - { true ColorSmartColorMatching } if - globaldict /ColorSmartColorMatching known - { Vivid ColorSmartTextAdjustment } if - -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *ColorSmart Graphics Vivid Color - - globaldict /ColorSmartColorMatching known - { Vivid ColorSmartGraphicsAdjustment } if - -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *ColorSmart Photos Match Color Across Printers - - globaldict /ColorSmartColorMatching known - { MatchScreen ColorSmartImageAdjustment } if - -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *Text Halftone Detail - - globaldict /ColorSmartColorMatching known - { Detail ColorSmartTextHalftone } if - -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *Graphics Halftone Smooth - - globaldict /ColorSmartColorMatching known - { Smooth ColorSmartGraphicsHalftone } if - -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *Image Halftone Smooth - - globaldict /ColorSmartColorMatching known - { Smooth ColorSmartImageHalftone } if - -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *ColorSmart Auto - - globaldict /ColorSmartColorMatching known - { Vivid ColorSmartTextAdjustment } if - globaldict /ColorSmartColorMatching known - { Vivid ColorSmartGraphicsAdjustment } if - globaldict /ColorSmartColorMatching known - { MatchScreen ColorSmartImageAdjustment } if - globaldict /ColorSmartColorMatching known - { Detail ColorSmartTextHalftone } if - globaldict /ColorSmartColorMatching known - { Smooth ColorSmartGraphicsHalftone } if - globaldict /ColorSmartColorMatching known - { Smooth ColorSmartImageHalftone } if - /setscreen { pop pop pop } def - /setcolorscreen { pop pop pop pop pop pop pop pop pop pop pop pop } def - globaldict /ColorSmartColorMatching known - {true ColorSmartColorMatching } if - -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *OutputBin Upper -1 dict dup /OutputFaceUp false put setpagedevice -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *MediaType Plain Paper - -%%EndFeature -} stopped cleartomark -1 setlinecap 1 setlinejoin -/mysetup [ 0.240 0 0 -0.240 12.000 779.000 ] | -%%EndSetup - -userdict begin /savelevel0 save def end -%%Page: 1 1 -%%BeginPageSetup -[{ -%%BeginFeature: *Rear Feed Unit Not Installed - -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *VMOption 36 - 43 MB RAM - -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *Resolution 300dpi - -%%EndFeature -} stopped cleartomark -[{ -%%BeginFeature: *Duplex - -%%EndFeature -} stopped cleartomark -userdict begin /pagesave save def end mysetup concat colspRefresh : 1.000 1.000 1.000 sco 0 0 2550 3300 rf ; -%%EndPageSetup - -: 0 0 2454 3191 rc pagesave restore -Pscript_Win_Driver_Incr begin -%%BeginResource: file Pscript_Win_Graphics 2.0 0 -/SavedCTM null |/CTMsave{/SavedCTM SavedCTM currentmatrix |}b/CTMrestore{ -SavedCTM setmatrix}b/mp null |/ADO_mxRot null |/GDIHMatrix null | -/GDIHPatternDict 22 dict | GDIHPatternDict `/PatternType 1 |/PaintType 2 | -/Reps L2?{1}{5}? |/XStep 8 Reps mul |/YStep XStep |/BBox[0 0 XStep YStep]| -/TilingType 1 |/PaintProc{` 1 Lw[]0 setdash PaintData , exec E}b/FGnd null | -/BGnd null |/HS_Horizontal{horiz}b/HS_Vertical{vert}b/HS_FDiagonal{fdiag}b -/HS_BDiagonal{biag}b/HS_Cross{horiz vert}b/HS_DiagCross{fdiag biag}b/MaxXYStep -XStep YStep gt{XStep}{YStep}? |/horiz{Reps{0 4 M XStep 0 - 0 8 +}repeat 0 -8 -Reps mul + K}b/vert{Reps{4 0 M 0 YStep - 8 0 +}repeat 0 -8 Reps mul + K}b/biag -{Reps{0 0 M MaxXYStep @ - 0 YStep neg M MaxXYStep @ - 0 8 +}repeat 0 -8 Reps -mul + 0 YStep M 8 8 - K}b/fdiag{Reps{0 0 M MaxXYStep @ neg - 0 YStep M -MaxXYStep @ neg - 0 8 +}repeat 0 -8 Reps mul + MaxXYStep @ M 8 -8 - K}b E -/makehatch{GDIHPatternDict/PaintData 3 -1 $ put CTMsave GDIHMatrix setmatrix -GDIHPatternDict matrix mp CTMrestore ~ U ~ 2 ^ put}b/h0{/h0/HS_Horizontal -makehatch}b/h1{/h1/HS_Vertical makehatch}b/h2{/h2/HS_FDiagonal makehatch}b/h3{ -/h3/HS_BDiagonal makehatch}b/h4{/h4/HS_Cross makehatch}b/h5{/h5/HS_DiagCross -makehatch}b/GDIBWPatternDict 17 dict @ `/PatternType 1 |/PaintType L2?{1}{2}? -|/RepsV L2?{1}{6}? |/RepsH L2?{1}{5}? |/BBox[0 0 RepsH 1]|/TilingType 1 | -/XStep 1 |/YStep 1 |/Height 8 RepsV mul |/Width 8 |/mx[Width 0 0 Height neg 0 -Height]|/FGnd null |/BGnd null |/SetBGndFGnd L2?{{BGnd null ne{BGnd aload ! -sgco BBox aload ! 2 ^ sub ~ 3 ^ sub ~ rf}if FGnd null ne{FGnd aload ! sgco}if} -}{{}}? b/PaintProc{` SetBGndFGnd RepsH{Width Height F mx PaintData imagemask -Width 0 +}repeat E}b E |/GDIBWPatternMx null |/pfprep{save 4 1 $ -/PatternOfTheDay 4 1 $ GDIBWPatternDict `/PaintData ~ |/BGnd ~ |/FGnd ~ | E -CTMsave GDIBWPatternMx setmatrix GDIBWPatternDict matrix mp CTMrestore ~ !}b -/hrf null |/prf{pfprep ~ 6 1 $ 5 hrf restore}b/GraphInit{GDIHMatrix null eq{ -/SavedCTM matrix | : ADO_mxRot concat 0 0 snap + : 0.48 @ GDIHPatternDict ` -YStep mul ~ XStep mul ~ dsnap YStep V ~ XStep V ~ E +S/GDIHMatrix matrix -currentmatrix readonly | ; : 0.24 -0.24 +S GDIBWPatternDict ` Width Height E -dsnap +S/GDIBWPatternMx matrix currentmatrix readonly | ; ;}if}b/cirp{360 0 An -C}b/ellp{CTMsave + +S 0.5 0 M 0 0 0.5 360 0 An C CTMrestore}b/rrp{/rad ~ |/y2 -~ |/x2 ~ |/y1 ~ |/x1 ~ | x2 x1 add 2 V y1 M x1 y1 x1 y2 rad arct x1 y2 x2 y2 -rad arct x2 y2 x2 y1 rad arct x2 y1 x1 y1 rad arct C}b/RRp{CTMsave + +S/dyS ~ -|/dxS ~ | dxS 2 V 0 M 0 0 0 dyS 0.5 arct 0 dyS dxS dyS 0.5 arct dxS dyS dxS 0 -0.5 arct dxS 0 0 0 0.5 arct C CTMrestore}b -%%EndResource - -%%BeginResource: file Pscript_Win_Graphics_L1 2.0 0 -L2? not g{/arct{arcto ! ! ! !}b/GDIpattfill{@ ` BGnd null ne PaintType 2 eq -and{: BGnd aload ! sgco fEOFill{O}{L}? ; FGnd aload ! U/fGray 2 ^ put{2}{4}? --1 $}if E @ patterncalc : 4 ^/PaintType get 2 eq{fGray{6 -1 $ sg}{8 -3 $ sco}? -}if fEOFill{eoclip}{clip}? N patternfill ; N}b/hrf{/fGray 1 ^ 6 eq | -4 $ N rp -C/fEOFill F | GDIpattfill}b/hfMain{/fEOFill ~ |/fGray ~ | GDIpattfill}b/hf{T -hfMain}b/hfW{F hfMain}b/hs{currentpoint strokepath M hfW}b/pfMain{/fEOFill ~ | -pfprep GDIpattfill restore N}b/pf{T pfMain}b/pfW{F pfMain}b/ps{currentpoint -strokepath M pfW}b/mpstr 1 string |/mp{~ @ length 12 add dict copy ` -/PatternCTM matrix currentmatrix |/PatternMatrix ~ |/PatWidth XStep mpstr -length mul |/PatHeight YStep |/FontType 3 |/Encoding 256 array | 3 string 0 1 -255{Encoding ~ @ 3 ^ cvs cvn put}for !/FontMatrix matrix |/FontBBox BBox | -/BuildChar{! @ ` XStep 0 FontBBox aload ! setcachedevice/PaintProc , E : exec -;}b & E ~ @ 3 -1 $ definefont}b/patterncalc{` : PatternCTM setmatrix -PatternMatrix concat BBox aload ! ! ! + pathbbox ; PatHeight V ceiling 4 1 $ -PatWidth V ceiling 4 1 $ PatHeight V floor 4 1 $ PatWidth V floor 4 1 $ 2 ^ -sub cvi abs ~ 3 ^ sub cvi abs ~ 4 2 $ PatHeight mul ~ PatWidth mul ~ E}b -/patternfill{5 -1 $ @ ` Ji PatternCTM setmatrix PatternMatrix concat 0 2 ^ 2 ^ -M 0 1 mpstr length 1 sub{1 ^ mpstr 3 1 $ put}for ! 2 ^{currentpoint 5 ^{mpstr -S}repeat YStep add M}repeat ! ! ! ! E}b}e -%%EndResource - -%%BeginResource: file Pscript_Win_Graphics_L2 2.0 0 -L2? g{/mp/makepattern , |/hrf{6 eq setAorABC setpattern rectfill}b/hf{ -setAorABC setpattern O}b/hfW{setAorABC setpattern L}b/hs{setAorABC setpattern -K}b/pf{pfprep setpattern O restore N}b/pfW{pfprep setpattern L restore N}b/ps{ -pfprep setpattern K restore N}b}e -%%EndResource - -end reinitialize -userdict begin /pagesave save def end mysetup concat colspRefresh -: 0 0 0 sco 1 Lc 1 Lj solid 0 0 2454 3191 rc -1989 1646 N M 0 -419 - 1 Lw solid 0 0 0 sco K ; -N 1968.500 1645.500 19.500 88.603 -1.397 An -1 Lw 1 Lc 1 Lj 0 0 0 sco K : 0 0 2454 3191 rc -1931 1666 N M 38 0 - 0 0 0 sco K ; -N 1930.500 1685.500 19.500 -88.531 175.601 An -0 0 0 sco K : 0 0 2454 3191 rc -1911 2275 N M 0 -589 - 0 0 0 sco K ; : 1818 1632 636 23 rc : 1.000 1.000 1.000 sco 1872 1632 156 23 rf ; pagesave restore -Pscript_Win_Driver_Incr begin -%%BeginResource: file Pscript_Win_Encoding 2.0 0 -/bullets{{/bullet}repeat}b/ANSIEncoding[/grave/acute/circumflex/tilde/macron -/breve/dotaccent/dieresis/ring/cedilla/hungarumlaut/ogonek/caron/dotlessi 18 -bullets StandardEncoding 32 95 getinterval aload ! 3 bullets/quotesinglbase -/florin/quotedblbase/ellipsis/dagger/daggerdbl/circumflex/perthousand/Scaron -/guilsinglleft/OE 4 bullets/quoteleft/quoteright/quotedblleft/quotedblright -/bullet/endash/emdash/tilde/trademark/scaron/guilsinglright/oe 2 bullets -/Ydieresis/space/exclamdown/cent/sterling/currency/yen/brokenbar/section -/dieresis/copyright/ordfeminine/guillemotleft/logicalnot/hyphen/registered -/macron/degree/plusminus/twosuperior/threesuperior/acute/mu/paragraph -/periodcentered/cedilla/onesuperior/ordmasculine/guillemotright/onequarter -/onehalf/threequarters/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis -/Aring/AE/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute -/Icircumflex/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis -/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn/germandbls -/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla/egrave/eacute -/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis/eth/ntilde/ograve -/oacute/ocircumflex/otilde/odieresis/divide/oslash/ugrave/uacute/ucircumflex -/udieresis/yacute/thorn/ydieresis]| ANSIEncoding @ 39/quotesingle put 96/grave -put/ANSIEncodingOld ANSIEncoding 256 array copy | ANSIEncodingOld @[138 153 -154 169 172 174 177 178 179 181 185 188 189 190 208 215 221 222 240 247 253 -254]{/bullet put @}forall 166/bar put 176/ring put -%%EndResource - -%%BeginResource: file Pscript_Win_Text 2.0 0 -/TextInit{TextInitialised? not{/Pscript_Windows_Font & |/TextInitialised? T | -/fM[1 0 0 -1 0 0]|/mFM matrix |/iMat[1 0 0.212557 neg 1 0 0]|}if}b/xUP null | -/yUP null |/uW null |/xSP null |/ySP null |/sW null |/copyfont{1 ^ length add -dict `{1 ^/FID ne{|}{! !}?}forall & E}b/rF{3 copyfont @ `/Encoding -ANSIEncoding &/CharStrings known{CharStrings/Eth known not{! ANSIEncodingOld} -if}if | E}b/mF{findfont ~{@/Encoding get @ StandardEncoding eq{! T}{{ -ISOLatin1Encoding}stopped{! F}{eq}?{T}{@ ` T 32 1 127{Encoding 1 ^ get -StandardEncoding 3 -1 $ get eq and}for E}?}?}{F}?{rF}{3 copyfont}? ` -/OrigFontType ~ |/OrigFontName ~ | & E 2 ^ ~ definefont fM 5 4 -1 $ put fM 4 0 -put fM makefont Pscript_Windows_Font 3 1 $ put}b/xF{scalefont -Pscript_Windows_Font 3 1 $ put}b/xMF{mFM astore makefont Pscript_Windows_Font -3 1 $ put}b/xF2/scalefont , |/xMF2{mFM astore makefont}b/sLT{: Lw -M -currentpoint snap M 0 - 0 Lc K ;}b/sSU{N/uW ~ |/yUP ~ |/xUP ~ |}b/sU{xUP yUP -uW sLT}b/sST{N/sW ~ |/ySP ~ |/xSP ~ |}b/sT{xSP ySP sW sLT}b/sR{: + R 0 0 M}b -/sRxy{: matrix astore concat 0 0 M}b/eR/; , | -%%EndResource - -end reinitialize -userdict begin /pagesave save def end mysetup concat colspRefresh -: 0 0 0 sco 1 Lw 1 Lc 1 Lj 1818 1632 636 23 rc 0 0 0 sco %%IncludeFont: Helvetica -(F0) cvn -0.950 - (Helvetica) cvn /Type1 -T -(Helvetica) cvn -mF -(F0_20) cvn -F0 -20 -xF -F0_20 -Ji -1872 1632 M --0.012 0 (product = product)A -; -1989 1304 N M 7 34 - -15 0 - 8 -34 - C : 0 0 0 sco O ; 1 Lw 1 Lc 1 Lj 0 0 0 sco K : 0 0 2454 3191 rc -2135 1050 N M -906 0 - 0 0 0 sco K ; : 1408 1060 1026 23 rc : 1.000 1.000 1.000 sco 1462 1060 164 23 rf ; 0 0 0 sco F0_20 -Ji -1462 1060 M -0.002 0 (product = program)A -; -1742 1050 N M -33 7 - 0 -15 - 33 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -2093 1250 N M -1848 0 - 0 0 0 sco K ; : 1014 1260 1026 23 rc : 1.000 1.000 1.000 sco 1068 1260 164 23 rf ; 0 0 0 sco F0_20 -Ji -1068 1260 M -0.002 0 (product = program)A -; -1742 1250 N M -33 7 - 0 -15 - 33 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -1798 1151 N M -946 0 - 0 0 0 sco K ; : 1204 1161 1026 23 rc : 1.000 1.000 1.000 sco 1258 1161 156 23 rf ; 0 0 0 sco F0_20 -Ji -1258 1161 M --0.012 0 (product = product)A -; -1742 1151 N M -33 7 - 0 -15 - 33 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -717 1719 N M 0 689 - 0 0 0 sco K ; -N 736.500 1718.500 19.500 -88.531 175.601 An -0 0 0 sco K : 0 0 2454 3191 rc -864 1699 N M -127 0 - 0 0 0 sco K ; -N 863.500 1678.500 19.500 88.603 -1.397 An -0 0 0 sco K : 0 0 2454 3191 rc -884 1464 N M 0 215 - 0 0 0 sco K ; : 681 1687 918 23 rc : 1.000 1.000 1.000 sco 735 1687 130 23 rf ; 0 0 0 sco F0_20 -Ji -735 1687 M --0.115 0 (userid = userid)A -; -717 2221 N M -8 -33 - 15 0 - -7 33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -649 1684 N M 0 737 - 0 0 0 sco K ; -N 628.500 1683.500 19.500 1.397 -91.469 An -0 0 0 sco K : 0 0 2454 3191 rc -334 1664 N M 295 0 - 0 0 0 sco K ; : 513 1635 918 23 rc : 1.000 1.000 1.000 sco 567 1635 130 23 rf ; 0 0 0 sco F0_20 -Ji -567 1635 M --0.115 0 (userid = userid)A -; -649 2221 N M -8 -33 - 15 0 - -7 33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -837 1882 N M 0 378 - 0 0 0 sco K ; -N 856.500 1881.500 19.500 -88.531 175.601 An -0 0 0 sco K : 0 0 2454 3191 rc -1121 1862 N M -264 0 - 0 0 0 sco K ; : 0 0 2454 3191 rc -1467 1862 N M -346 0 - 0 0 0 sco K ; : 869 1850 756 23 rc : 1.000 1.000 1.000 sco 923 1850 113 23 rf ; 0 0 0 sco F0_20 -Ji -923 1850 M --0.078 0 (userid = who)A -; -837 2221 N M -8 -33 - 15 0 - -7 33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -962 2267 N M -94 0 - 0 0 0 sco K ; -N 961.500 2246.500 19.500 88.603 -1.397 An -0 0 0 sco K : 0 0 2454 3191 rc -982 2105 N M 0 142 - 0 0 0 sco K ; -N 1001.500 2104.500 19.500 -88.531 175.601 An -0 0 0 sco K : 0 0 2454 3191 rc -1347 2085 N M -345 0 - 0 0 0 sco K ; : 872 2164 756 23 rc : 1.000 1.000 1.000 sco 926 2164 113 23 rf ; 0 0 0 sco F0_20 -Ji -926 2164 M --0.078 0 (userid = who)A -; -872 2267 N M 33 -8 - 0 15 - -33 -7 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -978 2437 N M -158 0 - 0 0 0 sco K ; -N 977.500 2416.500 19.500 88.603 -1.397 An -0 0 0 sco K : 0 0 2454 3191 rc -998 2345 N M 0 72 - 0 0 0 sco K ; -N 1017.500 2344.500 19.500 -88.531 175.601 An -0 0 0 sco K : 0 0 2454 3191 rc -1212 2325 N M -194 0 - 0 0 0 sco K ; : 888 2369 756 23 rc : 1.000 1.000 1.000 sco 942 2369 113 23 rf ; 0 0 0 sco F0_20 -Ji -942 2369 M --0.078 0 (userid = who)A -; -872 2437 N M 33 -7 - 0 15 - -33 -8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -829 2672 N M 0 -152 - 0 0 0 sco K ; -N 848.500 2671.500 19.500 178.531 85.815 An -0 0 0 sco K : 0 0 2454 3191 rc -1194 2692 N M -345 0 - 0 0 0 sco K ; : 700 2697 1242 23 rc : 1.000 1.000 1.000 sco 754 2697 184 23 rf ; 0 0 0 sco F0_20 -Ji -754 2697 M --0.104 0 (userid = submitter_id)A -; -829 2620 N M 8 33 - -15 0 - 7 -33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -570 2708 N M 0 -156 - 0 0 0 sco K ; -N 589.500 2707.500 19.500 178.531 85.815 An -0 0 0 sco K : 0 0 2454 3191 rc -773 2728 N M -183 0 - 0 0 0 sco K ; -N 772.500 2747.500 19.500 1.397 -91.469 An -0 0 0 sco K : 0 0 2454 3191 rc -793 2836 N M 0 -88 - 0 0 0 sco K ; : 572 2716 756 23 rc : 1.000 1.000 1.000 sco 626 2716 113 23 rf ; 0 0 0 sco F0_20 -Ji -626 2716 M --0.078 0 (userid = who)A -; -570 2620 N M 8 33 - -15 0 - 7 -33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -1554 2379 N M 690 0 - 0 0 0 sco K ; -N 1553.500 2358.500 19.500 178.531 85.815 An -0 0 0 sco K : 0 0 2454 3191 rc -1534 2032 N M 0 327 - 0 0 0 sco K ; : 1427 2384 918 23 rc : 1.000 1.000 1.000 sco 1481 2384 140 23 rf ; 0 0 0 sco F0_20 -Ji -1481 2384 M --0.192 0 (bug_id = bug_id)A -; -1826 2379 N M -33 8 - 0 -15 - 33 7 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -1306 2476 N M 620 0 - 0 0 0 sco K ; -N 1305.500 2455.500 19.500 178.531 85.815 An -0 0 0 sco K : 0 0 2454 3191 rc -1286 2224 N M 0 232 - 0 0 0 sco K ; : 1179 2481 918 23 rc : 1.000 1.000 1.000 sco 1233 2481 140 23 rf ; 0 0 0 sco F0_20 -Ji -1233 2481 M --0.192 0 (bug_id = bug_id)A -; -1826 2476 N M -33 8 - 0 -15 - 33 7 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -1693 2787 N M 140 0 - 0 0 0 sco K ; -N 1692.500 2766.500 19.500 178.531 85.815 An -0 0 0 sco K : 0 0 2454 3191 rc -1673 2652 N M 0 115 - 0 0 0 sco K ; -N 1652.500 2651.500 19.500 1.397 -91.469 An -0 0 0 sco K : 0 0 2454 3191 rc -1487 2632 N M 166 0 - 0 0 0 sco K ; : 1549 2697 905 23 rc : 1.000 1.000 1.000 sco 1603 2697 140 23 rf ; 0 0 0 sco F0_20 -Ji -1603 2697 M --0.192 0 (bug_id = bug_id)A -; -1826 2787 N M -33 7 - 0 -15 - 33 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -1953 2954 N M -880 0 - 0 0 0 sco K ; : 1321 2964 918 23 rc : 1.000 1.000 1.000 sco 1375 2964 140 23 rf ; 0 0 0 sco F0_20 -Ji -1375 2964 M --0.192 0 (bug_id = bug_id)A -; -1826 2954 N M -33 8 - 0 -15 - 33 7 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -326 2275 N M 314 0 - 0 0 0 sco K ; -N 325.500 2254.500 19.500 178.531 85.815 An -0 0 0 sco K : 0 0 2454 3191 rc -306 1933 N M 0 322 - 0 0 0 sco K ; : 204 2280 918 23 rc : 1.000 1.000 1.000 sco 258 2280 130 23 rf ; 0 0 0 sco F0_20 -Ji -258 2280 M --0.115 0 (userid = userid)A -; -426 2275 N M -33 7 - -1 -15 - 34 8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -224 2919 N M 0 -905 - 0 0 0 sco K ; : 107 2409 1026 23 rc : 1.000 1.000 1.000 sco 161 2409 126 23 rf ; 0 0 0 sco F0_20 -Ji -161 2409 M --0.075 0 (fieldid = fieldid)A -; -224 2819 N M -7 -34 - 15 0 - -8 34 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -360 2910 N M 573 0 - 0 0 0 sco K ; : 555 2920 1026 23 rc : 1.000 1.000 1.000 sco 609 2920 126 23 rf ; 0 0 0 sco F0_20 -Ji -609 2920 M --0.075 0 (fieldid = fieldid)A -; -542 2910 N M 34 -8 - 0 16 - -34 -8 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -2070 2339 N M 0 -475 - 0 0 0 sco K ; : 1946 2044 508 23 rc : 1.000 1.000 1.000 sco 2000 2044 140 23 rf ; 0 0 0 sco F0_20 -Ji -2000 2044 M --0.192 0 (bug_id = bug_id)A -; -2070 2227 N M -7 -33 - 15 0 - -8 33 - C : 0 0 0 sco O ; 0 0 0 sco K : 0 0 2454 3191 rc -1726 2297 N M 372 0 - 0 0 0 sco K ; -N 1725.500 2276.500 19.500 178.531 85.815 An -0 0 0 sco K : 0 0 2454 3191 rc -1706 1859 N M 0 418 - 0 0 0 sco K ; -N 1685.500 1858.500 19.500 1.397 -91.469 An -0 0 0 sco K : 0 0 2454 3191 rc -1537 1839 N M 149 0 - 0 0 0 sco K ; : 1582 2056 872 23 rc : 1.000 1.000 1.000 sco 1636 2056 140 23 rf ; 0 0 0 sco F0_20 -Ji -1636 2056 M --0.192 0 (bug_id = bug_id)A -; -1826 2297 N M -33 8 - 0 -15 - 33 7 - C : 0 0 0 sco O ; 0 0 0 sco K -174 1137 N M 416 206 rr : 1.000 1.000 1.000 sco O ; 0 Lc 0 Lj 0 0 0 sco K : 235 1142 345 32 rc 0 0 0 sco (F0_27) cvn -F0 -27 -xF -F0_27 -Ji -308 1142 M -0.093 0 (components)A -; : 0 0 2454 3191 rc -174 1177 N M 416 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 184 1180 196 32 rc 0 0 0 sco F0_27 -Ji -184 1180 M --0.106 0 (value)A -; : 400 1180 190 32 rc 0 0 0 sco F0_27 -Ji -400 1180 M -0.058 0 (tinytext)A -; : 184 1213 196 32 rc 0 0 0 sco F0_27 -Ji -184 1213 M --0.074 0 (program)A -; : 400 1213 190 32 rc 0 0 0 sco F0_27 -Ji -400 1213 M --0.001 0 (VARCHAR$64$)A -; : 184 1246 196 32 rc 0 0 0 sco F0_27 -Ji -184 1246 M --0.002 0 (initialowner)A -; : 400 1246 190 32 rc 0 0 0 sco F0_27 -Ji -400 1246 M -0.058 0 (tinytext)A -; : 184 1279 196 32 rc 0 0 0 sco F0_27 -Ji -184 1279 M -0.151 0 (initialqacontact)A -; : 400 1279 190 32 rc 0 0 0 sco F0_27 -Ji -400 1279 M -0.058 0 (tinytext)A -; : 184 1312 196 29 rc 0 0 0 sco F0_27 -Ji -184 1312 M -0.132 0 (description)A -; : 400 1312 190 29 rc 0 0 0 sco F0_27 -Ji -400 1312 M --0.154 0 (mediumtext)A -; -643 1054 N M 320 143 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 665 1059 288 32 rc 0 0 0 sco F0_27 -Ji -738 1059 M -0.097 0 (milestones)A -; : 0 0 2454 3191 rc -643 1094 N M 320 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 653 1097 100 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -653 1097 M --0.106 0 (value)A --64 sU -; : 773 1097 190 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -773 1097 M --0.001 0 (VARCHAR$20$)A --180 sU -; : 653 1130 100 32 rc 0 0 0 sco F0_27 -Ji -653 1130 M -0.136 0 (product)A -; : 773 1130 190 32 rc 0 0 0 sco F0_27 -Ji -773 1130 M --0.001 0 (VARCHAR$64$)A -; : 653 1163 100 31 rc 0 0 0 sco F0_27 -Ji -653 1163 M -0.283 0 (sortkey)A -; : 773 1163 190 31 rc 0 0 0 sco F0_27 -Ji -773 1163 M -0.046 0 (smallint$6$)A -; -1742 1001 N M 432 303 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1832 1006 332 32 rc 0 0 0 sco F0_27 -Ji -1905 1006 M -0.182 0 (products)A -; : 0 0 2454 3191 rc -1742 1042 N M 432 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1752 1044 212 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1752 1044 M -0.136 0 (product)A --91 sU -; : 1984 1044 190 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1984 1044 M --0.001 0 (VARCHAR$64$)A --180 sU -; : 1752 1077 212 32 rc 0 0 0 sco F0_27 -Ji -1752 1077 M -0.132 0 (description)A -; : 1984 1077 190 32 rc 0 0 0 sco F0_27 -Ji -1984 1077 M --0.154 0 (mediumtext)A -; : 1752 1110 212 32 rc 0 0 0 sco F0_27 -Ji -1752 1110 M -0.039 0 (milestoneurl)A -; : 1984 1110 190 32 rc 0 0 0 sco F0_27 -Ji -1984 1110 M -0.058 0 (tinytext)A -; : 1752 1143 212 32 rc 0 0 0 sco F0_27 -Ji -1752 1143 M --0.048 0 (disallownew)A -; : 1984 1143 190 32 rc 0 0 0 sco F0_27 -Ji -1984 1143 M -0.148 0 (tinyint$4$)A -; : 1752 1176 212 32 rc 0 0 0 sco F0_27 -Ji -1752 1176 M -0.078 0 (votesperuser)A -; : 1984 1176 190 32 rc 0 0 0 sco F0_27 -Ji -1984 1176 M -0.046 0 (smallint$6$)A -; : 1752 1209 212 32 rc 0 0 0 sco F0_27 -Ji -1752 1209 M --0.113 0 (maxvotesperbug)A -; : 1984 1209 190 32 rc 0 0 0 sco F0_27 -Ji -1984 1209 M -0.046 0 (smallint$6$)A -; : 1752 1242 212 32 rc 0 0 0 sco F0_27 -Ji -1752 1242 M -0.032 0 (votestoconfirm)A -; : 1984 1242 190 32 rc 0 0 0 sco F0_27 -Ji -1984 1242 M -0.046 0 (smallint$6$)A -; : 1752 1275 212 27 rc 0 0 0 sco F0_27 -Ji -1752 1275 M -0.026 0 (defaultmilestone)A -; : 1984 1275 190 27 rc 0 0 0 sco F0_27 -Ji -1984 1275 M --0.001 0 (VARCHAR$20$)A -; -1052 964 N M 328 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1092 969 278 32 rc 0 0 0 sco F0_27 -Ji -1165 969 M -0.060 0 (versions)A -; : 0 0 2454 3191 rc -1052 1004 N M 328 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1062 1007 108 32 rc 0 0 0 sco F0_27 -Ji -1062 1007 M --0.106 0 (value)A -; : 1190 1007 190 32 rc 0 0 0 sco F0_27 -Ji -1190 1007 M -0.058 0 (tinytext)A -; : 1062 1040 108 32 rc 0 0 0 sco F0_27 -Ji -1062 1040 M --0.074 0 (program)A -; : 1190 1040 190 32 rc 0 0 0 sco F0_27 -Ji -1190 1040 M --0.001 0 (VARCHAR$64$)A -; -1282 1466 N M 382 207 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1358 1471 296 32 rc 0 0 0 sco F0_27 -Ji -1431 1471 M -0.077 0 (groups)A -; : 0 0 2454 3191 rc -1282 1506 N M 382 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1292 1509 147 32 rc 0 0 0 sco F0_27 -Ji -1292 1509 M -0.163 0 (bit)A -; : 1459 1509 205 32 rc 0 0 0 sco F0_27 -Ji -1459 1509 M -0.046 0 (bigint$20$)A -; : 1292 1542 147 32 rc 0 0 0 sco F0_27 -Ji -1292 1542 M --0.132 0 (name)A -; : 1459 1542 205 32 rc 0 0 0 sco F0_27 -Ji -1459 1542 M --0.002 0 (VARCHAR$255$)A -; : 1292 1575 147 32 rc 0 0 0 sco F0_27 -Ji -1292 1575 M -0.132 0 (description)A -; : 1459 1575 205 32 rc 0 0 0 sco F0_27 -Ji -1459 1575 M --0.131 0 (text)A -; : 1292 1608 147 32 rc 0 0 0 sco F0_27 -Ji -1292 1608 M -0.043 0 (isbuggroup)A -; : 1459 1608 205 32 rc 0 0 0 sco F0_27 -Ji -1459 1608 M -0.148 0 (tinyint$4$)A -; : 1292 1641 147 29 rc 0 0 0 sco F0_27 -Ji -1292 1641 M --0.105 0 (userregexp)A -; : 1459 1641 205 29 rc 0 0 0 sco F0_27 -Ji -1459 1641 M -0.058 0 (tinytext)A -; -671 1361 N M 426 207 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 736 1366 351 32 rc 0 0 0 sco F0_27 -Ji -809 1366 M -0.121 0 (logincookies)A -; : 0 0 2454 3191 rc -671 1401 N M 426 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 681 1404 191 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -681 1404 M -0.162 0 (cookie)A --79 sU -; : 892 1404 205 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -892 1404 M --0.043 0 (mediumint$9$)A --157 sU -; : 681 1437 191 32 rc 0 0 0 sco F0_27 -Ji -681 1437 M -0.080 0 (userid)A -; : 892 1437 205 32 rc 0 0 0 sco F0_27 -Ji -892 1437 M --0.043 0 (mediumint$9$)A -; : 681 1470 191 32 rc 0 0 0 sco F0_27 -Ji -681 1470 M -0.151 0 (cryptpassword)A -; : 892 1470 205 32 rc 0 0 0 sco F0_27 -Ji -892 1470 M --0.001 0 (VARCHAR$64$)A -; : 681 1503 191 32 rc 0 0 0 sco F0_27 -Ji -681 1503 M -0.055 0 (hostname)A -; : 892 1503 205 32 rc 0 0 0 sco F0_27 -Ji -892 1503 M --0.002 0 (VARCHAR$128$)A -; : 681 1536 191 29 rc 0 0 0 sco F0_27 -Ji -681 1536 M -0.182 0 (lastused)A -; : 892 1536 205 29 rc 0 0 0 sco F0_27 -Ji -892 1536 M -0.036 0 (timestamp$14$)A -; -136 1493 N M 382 207 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 168 1498 340 32 rc 0 0 0 sco F0_27 -Ji -241 1498 M --0.006 0 (namedqueries)A -; : 0 0 2454 3191 rc -136 1533 N M 382 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 146 1536 162 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -146 1536 M -0.080 0 (userid)A --74 sU -; : 328 1536 190 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -328 1536 M --0.043 0 (mediumint$9$)A --157 sU -; : 146 1569 162 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -146 1569 M --0.132 0 (name)A --67 sU -; : 328 1569 190 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -328 1569 M --0.001 0 (VARCHAR$64$)A --180 sU -; : 146 1602 162 32 rc 0 0 0 sco F0_27 -Ji -146 1602 M --0.042 0 (watchfordiffs)A -; : 328 1602 190 32 rc 0 0 0 sco F0_27 -Ji -328 1602 M -0.148 0 (tinyint$4$)A -; : 146 1635 162 32 rc 0 0 0 sco F0_27 -Ji -146 1635 M -0.038 0 (linkinfooter)A -; : 328 1635 190 32 rc 0 0 0 sco F0_27 -Ji -328 1635 M -0.148 0 (tinyint$4$)A -; : 146 1668 162 29 rc 0 0 0 sco F0_27 -Ji -146 1668 M -0.095 0 (query)A -; : 328 1668 190 29 rc 0 0 0 sco F0_27 -Ji -328 1668 M --0.154 0 (mediumtext)A -; -1165 2554 N M 378 335 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1206 2559 327 32 rc 0 0 0 sco F0_27 -Ji -1279 2559 M -0.176 0 (attachments)A -; : 0 0 2454 3191 rc -1165 2595 N M 378 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1175 2597 165 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1175 2597 M -0.159 0 (attach_id)A --111 sU -; : 1360 2597 183 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1360 2597 M --0.043 0 (mediumint$9$)A --157 sU -; : 1175 2630 165 32 rc 0 0 0 sco F0_27 -Ji -1175 2630 M --0.009 0 (bug_id)A -; : 1360 2630 183 32 rc 0 0 0 sco F0_27 -Ji -1360 2630 M --0.043 0 (mediumint$9$)A -; : 1175 2663 165 32 rc 0 0 0 sco F0_27 -Ji -1175 2663 M -0.177 0 (creation_ts)A -; : 1360 2663 183 32 rc 0 0 0 sco F0_27 -Ji -1360 2663 M -0.036 0 (timestamp$14$)A -; : 1175 2696 165 32 rc 0 0 0 sco F0_27 -Ji -1175 2696 M -0.132 0 (description)A -; : 1360 2696 183 32 rc 0 0 0 sco F0_27 -Ji -1360 2696 M --0.154 0 (mediumtext)A -; : 1175 2729 165 32 rc 0 0 0 sco F0_27 -Ji -1175 2729 M --0.002 0 (mimetype)A -; : 1360 2729 183 32 rc 0 0 0 sco F0_27 -Ji -1360 2729 M --0.154 0 (mediumtext)A -; : 1175 2762 165 32 rc 0 0 0 sco F0_27 -Ji -1175 2762 M -0.209 0 (ispatch)A -; : 1360 2762 183 32 rc 0 0 0 sco F0_27 -Ji -1360 2762 M -0.148 0 (tinyint$4$)A -; : 1175 2795 165 32 rc 0 0 0 sco F0_27 -Ji -1175 2795 M --0.129 0 (filename)A -; : 1360 2795 183 32 rc 0 0 0 sco F0_27 -Ji -1360 2795 M --0.154 0 (mediumtext)A -; : 1175 2828 165 32 rc 0 0 0 sco F0_27 -Ji -1175 2828 M -0.133 0 (thedata)A -; : 1360 2828 183 32 rc 0 0 0 sco F0_27 -Ji -1360 2828 M --0.007 0 (longblob)A -; : 1175 2861 165 26 rc 0 0 0 sco F0_27 -Ji -1175 2861 M -0.080 0 (submitter_id)A -; : 1360 2861 183 26 rc 0 0 0 sco F0_27 -Ji -1360 2861 M --0.043 0 (mediumint$9$)A -; -1826 2227 N M 456 815 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1951 2232 321 32 rc 0 0 0 sco F0_27 -Ji -2024 2232 M -0.116 0 (bugs)A -; : 0 0 2454 3191 rc -1826 2268 N M 456 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1836 2270 236 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1836 2270 M --0.009 0 (bug_id)A --81 sU -; : 2092 2270 190 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -2092 2270 M --0.043 0 (mediumint$9$)A --157 sU -; : 1836 2303 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2303 M -0.118 0 (groupset)A -; : 2092 2303 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2303 M -0.046 0 (bigint$20$)A -; : 1836 2336 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2336 M -0.129 0 (assigned_to)A -; : 2092 2336 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2336 M --0.043 0 (mediumint$9$)A -; : 1836 2369 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2369 M --0.006 0 (bug_file_loc)A -; : 2092 2369 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2369 M --0.131 0 (text)A -; : 1836 2402 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2402 M -0.078 0 (bug_severity)A -; : 2092 2402 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2402 M --0.132 0 (enum)A -; : 1836 2435 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2435 M -0.192 0 (bug_status)A -; : 2092 2435 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2435 M --0.132 0 (enum)A -; : 1836 2468 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2468 M -0.177 0 (creation_ts)A -; : 2092 2468 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2468 M -0.057 0 (datetime)A -; : 1836 2501 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2501 M -0.181 0 (delta_ts)A -; : 2092 2501 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2501 M -0.036 0 (timestamp$14$)A -; : 1836 2534 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2534 M -0.194 0 (short_desc)A -; : 2092 2534 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2534 M --0.154 0 (mediumtext)A -; : 1836 2567 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2567 M -0.244 0 (op_sys)A -; : 2092 2567 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2567 M --0.132 0 (enum)A -; : 1836 2600 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2600 M -0.125 0 (priority)A -; : 2092 2600 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2600 M --0.132 0 (enum)A -; : 1836 2633 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2633 M -0.136 0 (product)A -; : 2092 2633 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2633 M --0.001 0 (VARCHAR$64$)A -; : 1836 2666 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2666 M --0.046 0 (rep_platform)A -; : 2092 2666 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2666 M --0.132 0 (enum)A -; : 1836 2699 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2699 M -0.059 0 (reporter)A -; : 2092 2699 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2699 M --0.043 0 (mediumint$9$)A -; : 1836 2732 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2732 M --0.003 0 (version)A -; : 2092 2732 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2732 M --0.001 0 (VARCHAR$16$)A -; : 1836 2765 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2765 M -0.048 0 (component)A -; : 2092 2765 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2765 M --0.001 0 (VARCHAR$50$)A -; : 1836 2798 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2798 M -0.096 0 (resolution)A -; : 2092 2798 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2798 M --0.132 0 (enum)A -; : 1836 2831 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2831 M -0.089 0 (target_milestone)A -; : 2092 2831 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2831 M --0.001 0 (VARCHAR$20$)A -; : 1836 2864 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2864 M -0.192 0 (qa_contact)A -; : 2092 2864 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2864 M --0.043 0 (mediumint$9$)A -; : 1836 2897 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2897 M -0.111 0 (status_whiteboard)A -; : 2092 2897 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2897 M --0.154 0 (mediumtext)A -; : 1836 2930 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2930 M -0.094 0 (votes)A -; : 2092 2930 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2930 M --0.043 0 (mediumint$9$)A -; : 1836 2963 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2963 M -0.122 0 (keywords)A -; : 2092 2963 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2963 M --0.154 0 (mediumtext)A -; : 1836 2996 236 32 rc 0 0 0 sco F0_27 -Ji -1836 2996 M --0.005 0 (lastdiffed)A -; : 2092 2996 190 32 rc 0 0 0 sco F0_27 -Ji -2092 2996 M -0.057 0 (datetime)A -; : 1836 3029 236 11 rc 0 0 0 sco F0_27 -Ji -1836 3029 M --0.080 0 (everconfirmed)A -; : 2092 3029 190 11 rc 0 0 0 sco F0_27 -Ji -2092 3029 M -0.148 0 (tinyint$4$)A -; -768 2778 N M 330 239 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 781 2783 307 32 rc 0 0 0 sco F0_27 -Ji -854 2783 M -0.149 0 (bugs_activity)A -; : 0 0 2454 3191 rc -768 2819 N M 330 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 778 2821 133 32 rc 0 0 0 sco F0_27 -Ji -778 2821 M --0.009 0 (bug_id)A -; : 931 2821 167 32 rc 0 0 0 sco F0_27 -Ji -931 2821 M --0.043 0 (mediumint$9$)A -; : 778 2854 133 32 rc 0 0 0 sco F0_27 -Ji -778 2854 M --0.173 0 (who)A -; : 931 2854 167 32 rc 0 0 0 sco F0_27 -Ji -931 2854 M --0.043 0 (mediumint$9$)A -; : 778 2887 133 32 rc 0 0 0 sco F0_27 -Ji -778 2887 M --0.072 0 (bug_when)A -; : 931 2887 167 32 rc 0 0 0 sco F0_27 -Ji -931 2887 M -0.057 0 (datetime)A -; : 778 2920 133 32 rc 0 0 0 sco F0_27 -Ji -778 2920 M --0.075 0 (fieldid)A -; : 931 2920 167 32 rc 0 0 0 sco F0_27 -Ji -931 2920 M --0.043 0 (mediumint$9$)A -; : 778 2953 133 32 rc 0 0 0 sco F0_27 -Ji -778 2953 M --0.069 0 (oldvalue)A -; : 931 2953 167 32 rc 0 0 0 sco F0_27 -Ji -931 2953 M -0.058 0 (tinytext)A -; : 778 2986 133 29 rc 0 0 0 sco F0_27 -Ji -778 2986 M --0.131 0 (newvalue)A -; : 931 2986 167 29 rc 0 0 0 sco F0_27 -Ji -931 2986 M -0.058 0 (tinytext)A -; -1370 1784 N M 286 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1426 1789 220 32 rc 0 0 0 sco F0_27 -Ji -1499 1789 M -0.500 0 (cc)A -; : 0 0 2454 3191 rc -1370 1825 N M 286 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1380 1827 89 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1380 1827 M --0.009 0 (bug_id)A --81 sU -; : 1489 1827 167 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1489 1827 M --0.043 0 (mediumint$9$)A --157 sU -; : 1380 1860 89 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1380 1860 M --0.173 0 (who)A --49 sU -; : 1489 1860 167 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1489 1860 M --0.043 0 (mediumint$9$)A --157 sU -; -178 2819 N M 364 207 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 237 2824 295 32 rc 0 0 0 sco F0_27 -Ji -310 2824 M --0.061 0 (fielddefs)A -; : 0 0 2454 3191 rc -178 2859 N M 364 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 188 2862 144 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -188 2862 M --0.075 0 (fieldid)A --70 sU -; : 352 2862 190 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -352 2862 M --0.043 0 (mediumint$9$)A --157 sU -; : 188 2895 144 32 rc 0 0 0 sco F0_27 -Ji -188 2895 M --0.132 0 (name)A -; : 352 2895 190 32 rc 0 0 0 sco F0_27 -Ji -352 2895 M --0.001 0 (VARCHAR$64$)A -; : 188 2928 144 32 rc 0 0 0 sco F0_27 -Ji -188 2928 M -0.132 0 (description)A -; : 352 2928 190 32 rc 0 0 0 sco F0_27 -Ji -352 2928 M --0.154 0 (mediumtext)A -; : 188 2961 144 32 rc 0 0 0 sco F0_27 -Ji -188 2961 M --0.067 0 (mailhead)A -; : 352 2961 190 32 rc 0 0 0 sco F0_27 -Ji -352 2961 M -0.148 0 (tinyint$4$)A -; : 188 2994 144 29 rc 0 0 0 sco F0_27 -Ji -188 2994 M -0.283 0 (sortkey)A -; : 352 2994 190 29 rc 0 0 0 sco F0_27 -Ji -352 2994 M -0.046 0 (smallint$6$)A -; -1954 1803 N M 330 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1988 1808 286 32 rc 0 0 0 sco F0_27 -Ji -2061 1808 M -0.122 0 (keywords)A -; : 0 0 2454 3191 rc -1954 1843 N M 330 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1964 1846 133 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1964 1846 M --0.009 0 (bug_id)A --81 sU -; : 2117 1846 167 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -2117 1846 M --0.043 0 (mediumint$9$)A --157 sU -; : 1964 1879 133 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1964 1879 M -0.053 0 (keywordid)A --122 sU -; : 2117 1879 167 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -2117 1879 M -0.046 0 (smallint$6$)A --125 sU -; -1104 2179 N M 330 175 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1134 2184 290 32 rc 0 0 0 sco F0_27 -Ji -1207 2184 M -0.161 0 (longdescs)A -; : 0 0 2454 3191 rc -1104 2220 N M 330 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1114 2222 133 32 rc 0 0 0 sco F0_27 -Ji -1114 2222 M --0.009 0 (bug_id)A -; : 1267 2222 167 32 rc 0 0 0 sco F0_27 -Ji -1267 2222 M --0.043 0 (mediumint$9$)A -; : 1114 2255 133 32 rc 0 0 0 sco F0_27 -Ji -1114 2255 M --0.173 0 (who)A -; : 1267 2255 167 32 rc 0 0 0 sco F0_27 -Ji -1267 2255 M --0.043 0 (mediumint$9$)A -; : 1114 2288 133 32 rc 0 0 0 sco F0_27 -Ji -1114 2288 M --0.072 0 (bug_when)A -; : 1267 2288 167 32 rc 0 0 0 sco F0_27 -Ji -1267 2288 M -0.057 0 (datetime)A -; : 1114 2321 133 31 rc 0 0 0 sco F0_27 -Ji -1114 2321 M --0.008 0 (thetext)A -; : 1267 2321 167 31 rc 0 0 0 sco F0_27 -Ji -1267 2321 M --0.154 0 (mediumtext)A -; -426 2221 N M 446 399 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 532 2226 330 32 rc 0 0 0 sco F0_27 -Ji -605 2226 M --0.003 0 (profiles)A -; : 0 0 2454 3191 rc -426 2262 N M 446 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 436 2264 211 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -436 2264 M -0.080 0 (userid)A --74 sU -; : 667 2264 205 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -667 2264 M --0.043 0 (mediumint$9$)A --157 sU -; : 436 2297 211 32 rc 0 0 0 sco F0_27 -Ji -436 2297 M --0.056 0 (login_name)A -; : 667 2297 205 32 rc 0 0 0 sco F0_27 -Ji -667 2297 M --0.002 0 (VARCHAR$255$)A -; : 436 2330 211 32 rc 0 0 0 sco F0_27 -Ji -436 2330 M -0.058 0 (password)A -; : 667 2330 205 32 rc 0 0 0 sco F0_27 -Ji -667 2330 M --0.001 0 (VARCHAR$16$)A -; : 436 2363 211 32 rc 0 0 0 sco F0_27 -Ji -436 2363 M -0.151 0 (cryptpassword)A -; : 667 2363 205 32 rc 0 0 0 sco F0_27 -Ji -667 2363 M --0.001 0 (VARCHAR$64$)A -; : 436 2396 211 32 rc 0 0 0 sco F0_27 -Ji -436 2396 M --0.067 0 (realname)A -; : 667 2396 205 32 rc 0 0 0 sco F0_27 -Ji -667 2396 M --0.002 0 (VARCHAR$255$)A -; : 436 2429 211 32 rc 0 0 0 sco F0_27 -Ji -436 2429 M -0.118 0 (groupset)A -; : 667 2429 205 32 rc 0 0 0 sco F0_27 -Ji -667 2429 M -0.046 0 (bigint$20$)A -; : 436 2462 211 32 rc 0 0 0 sco F0_27 -Ji -436 2462 M -0.026 0 (emailnotification)A -; : 667 2462 205 32 rc 0 0 0 sco F0_27 -Ji -667 2462 M --0.132 0 (enum)A -; : 436 2495 211 32 rc 0 0 0 sco F0_27 -Ji -436 2495 M --0.006 0 (disabledtext)A -; : 667 2495 205 32 rc 0 0 0 sco F0_27 -Ji -667 2495 M --0.154 0 (mediumtext)A -; : 436 2528 211 32 rc 0 0 0 sco F0_27 -Ji -436 2528 M --0.004 0 (newemailtech)A -; : 667 2528 205 32 rc 0 0 0 sco F0_27 -Ji -667 2528 M -0.148 0 (tinyint$4$)A -; : 436 2561 211 32 rc 0 0 0 sco F0_27 -Ji -436 2561 M -0.097 0 (mybugslink)A -; : 667 2561 205 32 rc 0 0 0 sco F0_27 -Ji -667 2561 M -0.148 0 (tinyint$4$)A -; : 436 2594 211 24 rc 0 0 0 sco F0_27 -Ji -436 2594 M -0.148 0 (blessgroupset)A -; : 667 2594 205 24 rc 0 0 0 sco F0_27 -Ji -667 2594 M -0.046 0 (bigint$20$)A -; -150 1818 N M 374 239 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 171 1823 343 32 rc 0 0 0 sco F0_27 -Ji -244 1823 M -0.086 0 (profiles_activity)A -; : 0 0 2454 3191 rc -150 1858 N M 374 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 160 1861 177 32 rc 0 0 0 sco F0_27 -Ji -160 1861 M -0.080 0 (userid)A -; : 357 1861 167 32 rc 0 0 0 sco F0_27 -Ji -357 1861 M --0.043 0 (mediumint$9$)A -; : 160 1894 177 32 rc 0 0 0 sco F0_27 -Ji -160 1894 M --0.173 0 (who)A -; : 357 1894 167 32 rc 0 0 0 sco F0_27 -Ji -357 1894 M --0.043 0 (mediumint$9$)A -; : 160 1927 177 32 rc 0 0 0 sco F0_27 -Ji -160 1927 M --0.043 0 (profiles_when)A -; : 357 1927 167 32 rc 0 0 0 sco F0_27 -Ji -357 1927 M -0.057 0 (datetime)A -; : 160 1960 177 32 rc 0 0 0 sco F0_27 -Ji -160 1960 M --0.075 0 (fieldid)A -; : 357 1960 167 32 rc 0 0 0 sco F0_27 -Ji -357 1960 M --0.043 0 (mediumint$9$)A -; : 160 1993 177 32 rc 0 0 0 sco F0_27 -Ji -160 1993 M --0.069 0 (oldvalue)A -; : 357 1993 167 32 rc 0 0 0 sco F0_27 -Ji -357 1993 M -0.058 0 (tinytext)A -; : 160 2026 177 28 rc 0 0 0 sco F0_27 -Ji -160 2026 M --0.131 0 (newvalue)A -; : 357 2026 167 28 rc 0 0 0 sco F0_27 -Ji -357 2026 M -0.058 0 (tinytext)A -; -1289 1975 N M 286 143 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1326 1980 239 32 rc 0 0 0 sco F0_27 -Ji -1399 1980 M -0.094 0 (votes)A -; : 0 0 2454 3191 rc -1289 2016 N M 286 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1299 2018 89 32 rc 0 0 0 sco F0_27 -Ji -1299 2018 M --0.173 0 (who)A -; : 1408 2018 167 32 rc 0 0 0 sco F0_27 -Ji -1408 2018 M --0.043 0 (mediumint$9$)A -; : 1299 2051 89 32 rc 0 0 0 sco F0_27 -Ji -1299 2051 M --0.009 0 (bug_id)A -; : 1408 2051 167 32 rc 0 0 0 sco F0_27 -Ji -1408 2051 M --0.043 0 (mediumint$9$)A -; : 1299 2084 89 32 rc 0 0 0 sco F0_27 -Ji -1299 2084 M -0.192 0 (count)A -; : 1408 2084 167 32 rc 0 0 0 sco F0_27 -Ji -1408 2084 M -0.046 0 (smallint$6$)A -; -1914 755 N M 342 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1927 760 319 32 rc 0 0 0 sco F0_27 -Ji -2000 760 M -0.075 0 (dependencies)A -; : 0 0 2454 3191 rc -1914 796 N M 342 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1924 798 145 32 rc 0 0 0 sco F0_27 -Ji -1924 798 M -0.137 0 (blocked)A -; : 2089 798 167 32 rc 0 0 0 sco F0_27 -Ji -2089 798 M --0.043 0 (mediumint$9$)A -; : 1924 831 145 32 rc 0 0 0 sco F0_27 -Ji -1924 831 M -0.045 0 (dependson)A -; : 2089 831 167 32 rc 0 0 0 sco F0_27 -Ji -2089 831 M --0.043 0 (mediumint$9$)A -; -1548 755 N M 302 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1564 760 276 32 rc 0 0 0 sco F0_27 -Ji -1637 760 M -0.145 0 (duplicates)A -; : 0 0 2454 3191 rc -1548 796 N M 302 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1558 798 105 32 rc 0 0 0 sco F0_27 -Ji -1558 798 M --0.083 0 (dupe_of)A -; : 1683 798 167 32 rc 0 0 0 sco F0_27 -Ji -1683 798 M --0.043 0 (mediumint$9$)A -; : 1558 831 105 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1558 831 M --0.012 0 (dupe)A --60 sU -; : 1683 831 167 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1683 831 M --0.043 0 (mediumint$9$)A --157 sU -; -1058 728 N M 364 143 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 1091 733 321 32 rc 0 0 0 sco F0_27 -Ji -1164 733 M -0.041 0 (keyworddefs)A -; : 0 0 2454 3191 rc -1058 769 N M 364 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 1068 771 144 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1068 771 M --0.003 0 (id)A --21 sU -; : 1232 771 190 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -1232 771 M -0.046 0 (smallint$6$)A --125 sU -; : 1068 804 144 32 rc 0 0 0 sco F0_27 -Ji -1068 804 M --0.132 0 (name)A -; : 1232 804 190 32 rc 0 0 0 sco F0_27 -Ji -1232 804 M --0.001 0 (VARCHAR$64$)A -; : 1068 837 144 32 rc 0 0 0 sco F0_27 -Ji -1068 837 M -0.132 0 (description)A -; : 1232 837 190 32 rc 0 0 0 sco F0_27 -Ji -1232 837 M --0.154 0 (mediumtext)A -; -170 696 N M 346 175 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 205 701 301 32 rc 0 0 0 sco F0_27 -Ji -278 701 M --0.007 0 (shadowlog)A -; : 0 0 2454 3191 rc -170 737 N M 346 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 180 739 133 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -180 739 M --0.003 0 (id)A --21 sU -; : 333 739 183 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -333 739 M -0.069 0 (int$11$)A --77 sU -; : 180 772 133 32 rc 0 0 0 sco F0_27 -Ji -180 772 M -0.497 0 (ts)A -; : 333 772 183 32 rc 0 0 0 sco F0_27 -Ji -333 772 M -0.036 0 (timestamp$14$)A -; : 180 805 133 32 rc 0 0 0 sco F0_27 -Ji -180 805 M -0.051 0 (reflected)A -; : 333 805 183 32 rc 0 0 0 sco F0_27 -Ji -333 805 M -0.148 0 (tinyint$4$)A -; : 180 838 133 31 rc 0 0 0 sco F0_27 -Ji -180 838 M --0.076 0 (command)A -; : 333 838 183 31 rc 0 0 0 sco F0_27 -Ji -333 838 M --0.154 0 (mediumtext)A -; -646 755 N M 308 116 rr : 1.000 1.000 1.000 sco O ; 0 0 0 sco K : 691 760 253 32 rc 0 0 0 sco F0_27 -Ji -764 760 M -0.095 0 (watch)A -; : 0 0 2454 3191 rc -646 796 N M 308 0 - 1 Lc 1 Lj 0 0 0 sco K ; : 656 798 111 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -656 798 M -0.068 0 (watcher)A --95 sU -; : 787 798 167 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -787 798 M --0.043 0 (mediumint$9$)A --157 sU -; : 656 831 111 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -656 831 M -0.065 0 (watched)A --101 sU -; : 787 831 167 32 rc 0 0 0 sco F0_27 -Ji -0 29 1 sSU -787 831 M --0.043 0 (mediumint$9$)A --157 sU -; : 0 0 2454 3191 rc -780 2186 N M -3 -403 - 459 -177 - 1 Lc 1 Lj [ 37 25 ] setdsh : 1.000 1.000 1.000 sco solid K ; 0 0 0 sco K ; : 0 0 2454 3191 rc -1686 1620 N M 160 243 - 0 331 - 1 Lc 1 Lj [ 37 25 ] setdsh : 1.000 1.000 1.000 sco solid K ; 0 0 0 sco K ; -LH -pagesave restore - -(%%[ Page: 1 ]%%) = -%%PageTrailer - -%%Trailer -%%DocumentNeededFonts: Helvetica -%%DocumentSuppliedFonts: -Pscript_Win_Driver_Incr dup /terminate get exec -savelevel0 restore -%%Pages: 1 -(%%[ LastPage ]%%) = -%%EOF -%-12345X@PJL EOJ -%-12345X \ No newline at end of file diff --git a/docs/sgml/faq.sgml b/docs/sgml/faq.sgml index 34b952b01..79fa528c4 100644 --- a/docs/sgml/faq.sgml +++ b/docs/sgml/faq.sgml @@ -620,6 +620,12 @@ progression states, also require adjusting the program logic to compensate for the change. + + There is no GUI for adding fields to Bugzilla at this + time. You can follow development of this feature at + http://bugzilla.mozilla.org/show_bug.cgi?id=91037 + @@ -633,42 +639,62 @@ - - This was a late-breaking question for the Guide, so I just have to - quote the relevant newsgroup thread on it. - - -> AFAIK, most sites (even if they have SSI enabled) won't have #exec cmd -> enabled. Perhaps what would be better is a #include virtual and a -> footer.cgi the basically has the "require 'CGI.pl' and PutFooter command. -> -> Please note that under most configurations, this also requires naming -> the file from index.html to index.shtml (and making sure that it will -> still be reconized as an index). Personally, I think this is better on -> a per-installation basis (perhaps add something to the FAQ that says how -> to do this). - -Good point. Yeah, easy enough to do, that it shouldn't be a big deal for -someone to take it on if they want it. FAQ is a good place for it. - -> Dave Miller wrote: -> ->> I did a little experimenting with getting the command menu and footer on ->> the end of the index page while leaving it as an HTML file... ->> ->> I was successful. :) ->> ->> I added this line: ->> ->> ->> ->> Just before the </BODY> </HTML> at the end of the file. And it worked. ->> ->> Thought I'd toss that out there. Should I check this in? For those that ->> have SSI disabled, it'll act like a comment, so I wouldn't think it would ->> break anything. - + + It's possible to get the footer on the static index page using + Server Side Includes (SSI). The trick to doing this is making + sure that your web server is set up to allow SSI and specifically, + the #exec directive. You should also rename index.html + to index.shtml. + + + After you've done all that, you can add the following line to + index.shtml: + + +]]> + + + + + This line will be replaced with the actual HTML for the footer + when the page is requested, so you should put this line where you + want the footer to appear. + + + + Because this method depends on being able to use a #exec directive, + and most ISP's will not allow that, there is an alternative method. + You could have a small script (such as api.cgi) + that basically looks like: + + + + and then put this line in index.shtml. + + +]]> + + + + + This still requires being able to use Server Side Includes, if + this simply will not work for you, see bug 80183 + for a third option. + + @@ -804,21 +830,6 @@ someone to take it on if they want it. FAQ is a good place for it. - - - - Does Bugzilla allow fields to be added, changed or deleted? If I want to - customize the bug submission form to meet our needs, can I do that using our - terminology? - - - - - Yes. - - - - @@ -1221,20 +1232,11 @@ someone to take it on if they want it. FAQ is a good place for it. If you are using an alternate Mail Transport Agent (MTA other than sendmail), make sure the options given in the "processmail" script for all - instances of "sendmail" are correct for your MTA. If you are using Sendmail, - you may wish to delete the "-ODeliveryMode=deferred" option in the - "processmail" script for every invocation of "sendmail". (Be sure and leave - the "-t" option, though!) - - - A better alternative is to change the "-O" option to - "-ODeliveryMode=background". This prevents Sendmail from hanging your - Bugzilla Perl processes if the domain to which it must send mail - is unavailable. + instances of "sendmail" are correct for your MTA. - This is now a configurable parameter called "sendmailnow", available - from editparams.cgi. + If you are using Sendmail, try enabling "sendmailnow" in editparams.cgi. + If you are using Postfix, you will also need to enable sendmailnow. @@ -1315,12 +1317,21 @@ someone to take it on if they want it. FAQ is a good place for it. - Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home - directory) to see! If it all comes back, you're OK. If it doesn't come back - OK (i.e. any red letters), there are certain things Bugzilla can recover - from and certain things it can't. If it can't auto-recover, I hope you're - familiar with mysqladmin commands or have installed another way to manage - your database... + Run the sanity check utility + (./sanitycheck.cgi in the + Bugzilla_home directory) from your web browser to see! If + it finishes without errors, you're + probably OK. If it doesn't come back + OK (i.e. any red letters), there are certain things + Bugzilla can recover from and certain things it can't. If + it can't auto-recover, I hope you're familiar with + mysqladmin commands or have installed another way to + manage your database. Sanity Check, although it is a good + basic check on your database integrity, by no means is a + substitute for competent database administration and + avoiding deletion of data. It is not exhaustive, and was + created to do a basic check for the most common problems + in Bugzilla databases. @@ -1428,10 +1439,12 @@ someone to take it on if they want it. FAQ is a good place for it. - Delete everything from $BUZILLA_HOME/shadow. Bugzilla creates shadow - files there, with each filename corresponding to a - bug number. Also be sure to run syncshadowdb to make sure, if you are using - a shadow database, that the shadow database is current. + This should only happen with Bugzilla &bz-ver; if you are + using the shadow database feature, and your + shadow database is out of sync. Try running + syncshadowdb + to make sure your shadow + database is in synch with your primary database. @@ -1752,14 +1765,14 @@ A: Sure! Here ya go! - Try + Try this link to view current bugs or requests for enhancement for Bugzilla. - You can view bugs marked for 2.14 release - here. - This list includes bugs for the 2.14 release that have already + You can view bugs marked for 2.16 release + here. + This list includes bugs for the 2.16 release that have already been fixed and checked into CVS. Please consult the Bugzilla Project Page for details on how to @@ -1800,8 +1813,9 @@ A: Sure! Here ya go! - Enter a bug into bugzilla.mozilla.org for the "Webtools" product, - "Bugzilla" component. + Enter a bug into bugzilla.mozilla.org for the Bugzilla + product. diff --git a/docs/sgml/future.sgml b/docs/sgml/future.sgml index 1f4681a31..54f191349 100644 --- a/docs/sgml/future.sgml +++ b/docs/sgml/future.sgml @@ -4,11 +4,595 @@ The Future of Bugzilla Bugzilla's Future. Much of this is the present, now. - The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do - not have more information about it right now, and most of what - went into the "future" section is now present. That stuff was - blue-sky a year ago; MattyT should have me a new document - sometime... + Bugzilla's future is a constantly-changing thing, as various developers + scratch an itch when it comes to functionality. + Thus this section is very malleable, subject to change without notice, etc. + You'll probably also notice the lack of formatting. I apologize that it's + not quite as readable as the rest of the Guide. + + + + Bugzilla Blue Sky + +Customisability + + One of the major stumbling blocks of Bugzilla has been that it is too + rigid and does not adapt itself well enough to the needs of an + organisation. This has led to organisations making changes to the + Bugzilla code that need to be redone each new version of Bugzilla. + Bugzilla should attempt to move away from this to a world where this + doesn't need to occur. + + Most of the subsections in this section are currently explicit design + goals for the "Bugzilla 3" rewrite. This does not necessarily mean + that they will not occur before them in Bugzilla 2, but most are + significant undertakings. + + Field Customisation + + Many installations wish to customise the fields that appear on bug + reports. Current versions of Bugzilla offer limited + customisability. In particular, some fields can be turned off. + + However, many administrators wish to add their own fields, and rename + or otherwise modify existing fields. An architecture that supports + this would be extraordinarily useful. + + Indeed, many fields work similarly and could be abstracted into "field + types", so that an administrator need write little or no code to + support the new fields they desire. + + Possible field types include text (eg status whiteboard), numbers, + dates (eg report time), accounts (eg reporter, qa, cc), inter-bug + relationships (dependencies, duplicates), option groups (platform, os, + severity, priority, target milestone, version) etc. + + Ideally an administrator could configure their fields through a + Bugzilla interface that requires no code to be added. However, it is + highly unlikely this ideal will never be met, and in a similar way + that office applications have scripting languages, Bugzilla should + allow new field types to be written. + + Similarly, a common desire is for resolutions to be added or removed. + + Allocations + + ? + + Option Groups + + ? + + Relations + + ? + + Database Integrity + + Furthermore, it is desirable for administrators to be able to specify + rules that must or should apply between the fields on a bug report. + + For example, you might wish to specify that a bug with status ASSIGNED + must have a target milestone field that that is not untargetted. Or + that a bug with a certain number of votes should get ASSIGNED. Or + that the QA contact must be different from the assignee. + + "Must" relationships could be implemented by refusing to make changes + that violate the relationships, or alternatively, automatically + updating certain fields in order to satisfy the criteria. Which + occurs should be up to the administrator. + + "Should" relationships could be implemented by a combination of + emitting warnings on the process bug page, the same on notification + mails, or emitting periodic whine mails about the situation. Again, + which occurs should be up to the administrator. + + It should also be possible for whine mails to be emitted for "must" + relationships, as they might become violated through direct database + access, Bugzilla bugs, or because they were there before the + relationship was enforced. + + As well as implementing intra-bug constraints, it would be useful to + create inter-bug constraints. For example, a bug that is dependent on + another bug should not have an earlier milestone or greater priority + than that bug. + + Database Adaptability + + Often an administrator desires that fields adapt to the values of + other fields. For example, the value of a field might determine the + possible values of another field or even whether it appears (whether + it is "applicable"). + + Limited adaptability is present in Bugzilla 2, and only on the + "Product" field: + * The possible values of the target milestone, version and component + fields depend on the product. + * UNCONFIRMED can be turned off for specific products. + * Voting can be configured differently or turned off for different + products, and there is a separate user vote limits for each + product. + + It would be good if more adaptability was present, both in terms of + all fields relying on the product, as well as the ability to adapt + based on the value of all fields. + + Example ??? + + General adaptability raises the issue of circular references between + fields causing problems. One possible solution to this is to place + the fields in a total ordering and require a field refer only to the + previous fields. + + In Bugzilla 2, changing the product of a bug meant a second page would + appear that allowed you to choose a new milestone, component and + version, as those fields adapted themselves to the new product. This + page could be generalised to support all instances where: + * a field value must or might be changed because the possible values + have changed + * is going to drop off because it it is no longer applicable, and + this should be confirmed + * must be specified because it is suddenly applicable, and the + default value, if one exists, might not be acceptable + + Database Independence + + Currently Bugzilla only runs on the MySQL database. It would be + desirable for Bugzilla to run on other databases, because: + * Organisations may have existing database products they use and + would prefer to run a homogenous environment. + * Databases each have their own shortcomings, including MySQL. An + administrator might choose a database that would work better with + their Bugzilla. + + This raises the possibility that we could use features that are only + present in some databases, by appropriately falling back. For + example, in the MySQL world, we live without: + * record-level locking, instead we use table-level locking + * referential and record constraints, instead we checking code + * subselects, instead we use multiple queries and redundant "caches" + + Multiple Front Ends + + Currently Bugzilla is manipulated via the Web, and notifies via + E-Mail. It would be desirable for Bugzilla to easily support various + front ends. + + There is no reason that Bugzilla could not be controlled via a whole + range of front ends, including Web, E-Mail, IRC, ICQ, etc, and + similarly for how it notifies. It's also possible that we could + introduce a special Bugzilla client that uses its own protocol, for + maximum user productivity. + + Indeed a request reply might be returned via a totally different + transport method than was use to submit the request. + +Internationalisation + + Bugzilla currently supports only English. All of the field names, + user instructions, etc are written in English. It would be desirable + to allow "language packs" so Bugzilla can be easily used in + non-English speaking locales. + + To a degree field customisation supports this, because administrators + could specify their own fields names anyway. However, there will + always be some basic facilities not covered by this, and it is + desirable that the administrator's interface also is + internationalisable. + +Better Searching + + General Summary Reports + + Sometimes, the normal querying page leaves a lot to be desired. There + are other facilities already in place or which people have asked for: + + Most Doomed Reports - All Bugs or All Bugs In A Product, Categorised + On Assignee, Shows and Counts Number of Bugs For Each Assignee + Most Voted For Bugs - All Bugs, Categorised On Product, Shows Top Ten + Bugs Voters Most Want Fixed + Number of Open Bugs For An Assignee - Bug List, Categorised On + Developers, Counts Number of Bugs In Category + + The important thing to realise is that people want categorised reports + on all sorts of things - a general summary report. + + In a categorised report, you choose the subset of bugs you wish to + operate on (similar to how you would specify a query), and then + categorise them on one or more fields. + + For each category you display the count of the number of things in + that category. You can optionally display the bugs themselves, or + leave them out, just showing the counts. And you can optionally limit + the number of things (bugs or subcategories) that display in each + category. + + Such a mechanism would let you do all of the above and more. + Applications of this mechanism would only be recognised once it was + implemented. + + Related Bugs + + It would be nice to have a field where you could enter other bugs + related to the current bug. It would be handy for navigation and + possibly even finding duplicates. + + Column Specification Support + + Currently bug lists use the columns that you last used. This doesn't + work well for "prepackaged queries", where you followed a link. You + can probably add a column by specifying a sort column, but this is + difficult and suboptimal. + + Furthermore, I find that when I want to add a column to a bug list, + it's usually a one off and I would prefer it to go away for the next + query. Hence, it would be nice to specify the columns that appear on + the bug list (and general summary report) pages. The default query + mechanism should be able to let you specify your default columns. + + Advanced Querying Redesign + + ? + +Keywords + + People have a need to apply tags to bugs. In the beginning, people + placed designators in the summary and status whiteboard. However, + these fields were not designed for that, and so there were many flaws + with this system: + * They pollute the field with information that was never intended to + be present. + * Removing them with a bulk change is a difficult problem that has + too many pitfalls to implement. + * You can easily get the capitalisation wrong. + + Then dependencies were introduced (when?), and people realised that + they could use them for "tracking bugs". Again, dependencies were not + designed for that, and so there were more flaws, albeit different + ones, including: + * They aren't really bugs, so it's difficult to distinguish issues + from bugs. + * They can pollute bugs counts, and you must somehow exclude them + from queries. + * There is a whole lot of useless information on them. They have an + assignee but there is nothing to fix, and that person can get + whined at by Bugzilla. They have target milestones which must be + manually maintained. And so on. + + Finally, keywords were introduced (when?) for this purpose to remove + the need for these two systems. Unfortunately, the simple keywords + implementation was itself lacking in certain features provided by the + two previous systems, and has remained almost unchanged since its + inception. Furthermore, it could not be forseen that in large + installations, the sheer number of keywords could become unwieldly and + could lead to a movement back to the other systems. + + The keywords system was the right idea, however, and it remains so. + Fixing the keywords system is one of the most important Bugzilla + issues. + + Bringing Keywords Up To Par + + For the most part, keywords are very good at what they do. It is easy + to add and remove them (unlike summary/whiteboard designators), we can + simply see what issues are present on a bug (unlike tracking bugs), + and we do not confuse bugs with issues (unlike tracking bugs). + + However, there are still some "regressions" in the keyword system over + previous systems: + * Users wish to view the "dependency forest" of a keyword. While a + dependency tree is of one bug, a dependency forest is of a bug + list, and consists of a dependency tree for each member of the bug + list. Users can work around this with tracking bugs by creating a + tracking bug and viewing the dependency tree of that tracking bug. + * Users wish to specify the keywords that initially apply to a bug, + but instead they must edit the bug once it has already been + submitted. They can work around this with summary designators, + since they specify the summary at reporting time. + * Users wish to store or share a bug list that contains a keywords + column. Hence they wish to be able to specify what columns appear + in the bug list URL, as mentioned earlier. They can work around + this using summary designators, since almost all bug lists have a + summary column. + * Users wish to be able to view keywords on a bug list. However + often they are only interested in a small number of keywords. + Having a bug list with a keywords column means that all keywords + will appear on a bug list. This can take a substantial amount of + space where a bug has a lot of keywords, since the table columns + in Bugzilla adjust to the largest cell in that column. Hence + users wish to be able to specify which keywords should appear in + the bug list. In a very real sense, each keyword is a field unto + itself. Users can work around this by using summary designators, + since they keywords will share the space in the summary column. + * Users wish to know when bugs with a specific issue are resolved. + Hence they wish to be able to receive notifications on all the + bugs with a specific keyword. The introduction a generic watching + facility (also for things like watching all bugs in a component) + would achieve this. Users can work around this by using tracking + bugs, as dependencies have an existing way of detecting fixes to + bug a bug was blocked by. + + Dealing With The Keyword Overload + + At the time of writing, the mozilla.org installation has approximately + 100 keywords, and many more would be in use if the keywords system + didn't have the problems it does. + + Such a large number of keywords introduces logistical problems: + * It must be easy for someone to learn what a keyword means. If a + keyword is buried within a lot of other keywords, it can be + difficult to find. + * It must be easy to see what keywords are on a bug. If the number + of keywords is large, then this can be difficult. + + These lead some people to feel that there are "too many keywords". + + These problems are not without solutions however. It is harder to + find a list of designators or tracking bugs than it is a list of + keywords. + + The essential problem is it needs to be easy to find the keywords + we're interested in through the mass of keywords. + + Keyword Applicability + + As has been previously mentioned, it is desirable for fields to be + able to adapt to the values of other fields. This is certainly true + for keywords. Many keywords are simply not relevant because of the + bugs product, component, etc. + + Hence, by introducing keyword applicability, and not displaying + keywords that are not relevant to the current bug, or clearly + separating them, we can make the keyword overload problem less + significant. + + Currently when you click on "keywords" on a bug, you get a list of all + bugs. It would be desirable to introduce a list of keywords tailored + to a specific bug, that reports, in order: + * the keywords currently on the bug + * the keywords not currently on the bug, but applicable to the bug + * optionally, the keywords not applicable to the bug + + This essentially orders the keywords into three groups, where each + group is more important than the previous, and therefore appears + closer to the top. + + Keyword Grouping & Ordering + + We could further enhance both the global and bug specific keyword list + by grouping keywords. We should always have a "flat" view of + keywords, but other ways of viewing the keywords would be useful too. + + If keyword applicability was implemented, we could group keywords + based on their "applicability condition". Keywords that apply to all + bugs could be separated from keywords that apply to a specific + product, both on the global keyword list and the keyword list of a bug + that is in that product. + + We could specify groups of our own. For example, many keywords are in + a mutually exclusive group, essentially like radio buttons in a user + interface. This creates a natural grouping, although other groupings + occur (which depends on your keywords). + + It is possible that we could use collapsing/expanding operations on + "twisties" to only should the groups we are interested in. + + And instead of grouping keywords, we could order them on some metric + of usefulness, such as: + * when the keyword was last added to a bug + * how many bugs the keyword is on + * how many open bugs the keyword is on + + Opting Out Of Keywords + + Not all people are going to care about all keywords. Therefore it + makes sense that you may wish to specify which keywords you are + interested in, either on the bug page, or on notifications. + + Other keywords will therefore not bother users who are not interested + in them. + + Keyword Security + + Currently all keywords are available and editable to all people with + edit bugs access. This situation is clearly suboptimal. + + Although relying on good behaviour for people to not do what they + shouldn't works reasonably well on the mozilla.org, it is better to + enforce that behaviour - it can be breached through malice, accident + or ignorance. + + And in the situation where it is desirable for the presence or absence + of a keyword not to be revealed, organisations either need to be + content with the divulgence, or not use keywords at all. + + In the situation where they choose to divulge, introducing the ability + to restrict who can see the keyword would also reduce keyword + overload. + + Personal Keywords + + Keywords join together a set of bugs which would otherwise be + unrelated in the bug system. + + We allow users to store their own queries. However we don't allow + them to store their own keywords on a bug. This reduces the + usefulness of personal queries, since you cannot join a set of + unrelated bugs together in a way that you wish. Lists of bug numbers + can work, by they can only be used for small lists, and it is + impossible to share a list between multiple queries. + + Personal keywords are necessary to replace personal tracking bugs, as + they would not pollute the keyword space. Indeed, on many + installations this could remove some keywords out of the global + keyword space. + + In a similar vein and with similar effects, group keywords could be + introduced that are only available to members of a specific group. + + Keyword Restrictions + + Keywords are not islands unto themselves. Along with their potential + to be involved in the inter-field relationships mentioned earlier, + keywords can also be related to other keywords. + + Essentially, there are two possibilities: + * a set of keywords are mutually exclusive + * the presence of a keyword implies another keyword must be present + + Introduction of the ability to specify these restrictions would have + benefits. + + If mutually exclusive keywords were present on a bug, their removal + would fix up the database, as well as reducing the number of keywords + on that bug. + + In the situation where a keyword implies another keyword, there are + two possiblities as to how to handle the situation. + + The first is automatically add the keyword. This would fix up the + database, but it would increase the number of keywords on a bug. + + The second is to automatically remove the keyword, and alter queries + so they pick up the first keyword as well as the removed keyword. + This would fix up the database and reduce the number of keywords on a + bug, but it might confuse users who don't see the keyword. + Alternatively, the implied keywords could be listed separately. + +Notifications + + Every time a bug gets changed notifications get sent out to people + letting them know about what changes have been made. This is a + significant feature, and all sorts of questions can be raised, but + they mainly boil down to when they should be sent and what they should + look like. + + Changes You're Interested In + + As of version 2.12 users can specify what sort of changes they are + interested in receiving notifications for. However, this is still + limited. As yet there is no facility to specify which keywords you + care about, and whether you care about changes to fields such as the + QA contact changes. + Furthermore, often an unnecessary comment will go along with a change, + either because it is required, or the commenter is ignorant of how the + new system works. While explaining why you did something is useful, + merely commenting on what you did is not because that information is + already accessible view "Bug Activity". + + Because of this unnecessary comment, a lot of changes that would + otherwise not generate notifications for certain people do so, because + few people are willing to turn off comments. One way to deal with + this problem is to allow people to specify that their comments are + purely explanatory, and that anyone who is not interested in the + change will not be interested in the comment. + + Furthermore, one possible rationale for unnecessary comments is that + the bug activity does not display on the normal page and hence it is + difficult to cross reference comments and actions. Hence, it would be + beneficial to be able to do this. + + Bugs You're Watching + + Currently to receive a notification about a bug you need to have your + name on it. This is suboptimal because you need to know about a bug + before you can receive notifications on it. Often you are interested + in any bug with a field set to a specific value. For example, you + might be interested in all bugs with a specific product, component or + keyword. + + If someone could automatically receive notifications about these bugs, + it would make everyone's lives easier. Currently the default assignee + and QA contact for a component will automatically receive + notifications for + + Question: This moves half way to a BCC. + + Bulk Changes + + A very useful feature of Bugzilla is the ability to perform an action + on multiple bugs at once. However, this means that similar + notifications are currently generated for each bug modified. + + This can result in a torrent of notifications that can annoy. + + Furthermore, since the bugs are all changed close to each other in + time, it is easy for someone to mass delete all the notifications + generated by a bulk change and miss an unrelated notification in the + middle. + + These factors can lead to a tendency for people to delay bulk changes, + or avoid them entirely. This is suboptimal. + + It would be better if a bulk change generated only one notification + mail. This would vastly reduce the annoyance factor, and prevent + accidental deletion of notifications. + + One problem with this change is that some people separate out + notifications using filtering. This means that they would no longer + be match parts of a bulk change under different filtering rules. + + One possibility to resolve this is to allow people to specify groups + of bugs. All bugs within a group would go into the same + notification. The filters could then distinguish the different bug + groups. + + In any case, it is likely there would need to be a transition period + to allow people to alter their filters. + +Nominations + + ? + +Linking Bugzilla Installations + + The first example of linking Bugzilla installations together has is + the introduction of bug moving in version 2.12. However, it would be + useful to be able to link installations in more ways. + * Dependencies and other relationships between bugs in other + installations. This is difficult because dependencies are + synchronised on both bugs, so the installation that changes + dependencies would need to communicate the new state to the other + installation. It would also mean that relationships and + notifications that refer to other bugs would need to communicate + with the other installation. + * References to bugs in other installations. Currently if you type + "bug XXX" or "bug #XXX" where XXX is a number, you get an + automatic hyperlink to that bug. It would be useful if you could + say "YYY bug #XXX" where YYY is the name of another installation. + +Retirement + + ? + +Whiny Reports + + ? + + Group Redesign + + ? + + Hard Wrapping Comments + + Currently Bugzilla "hard wraps" its comments to a specific line size, + similar to E-Mail. This has various problems: + * The way it currently works, wrapping is done in the browser at + submission time using a non-standard HTML extension not supported + by some (uncommon) browsers. These browsers generate comments + that scroll off the right side of the screen. + * Because comments are of fixed width, when you expand your browser + window, the comments do not expand to fit available space. + + It would be much better to move to a world of soft wrapping, where the + browser wraps the text at display time, similar to a world processor. + And as in a word processor, soft wrapping does not preclude the + insertion of newlines. + + Hard wrapping is too entrenched into text E-Mail to fix, but we can + fix Bugzilla without causing any problems. The old content will still + be wrapped too early, but at least new content will work. + @@ -32,3 +616,4 @@ sgml-shorttag:t sgml-tag-region-if-active:t End: --> + diff --git a/docs/sgml/installation.sgml b/docs/sgml/installation.sgml index 547d466ba..9cf100fdb 100644 --- a/docs/sgml/installation.sgml +++ b/docs/sgml/installation.sgml @@ -616,6 +616,15 @@ bash# mkdir /usr/bonsaitools/bin bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl + + Alternately, you can simply run this perl one-liner to + change your path to perl in all the files in your Bugzilla + installation: + +perl -pi -e 's@#!/usr/bonsaitools/bin/perl@/usr/bin/perl@' *cgi *pl Bug.pm + + Change the second path to perl to match your installation. + @@ -1241,7 +1250,7 @@ bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \ -
+
UNIX Installation Instructions History This document was originally adapted from the Bonsai @@ -1252,9 +1261,8 @@ bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \ The February 25, 1999 re-write of this page was done by Ry4an Brase <ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt, Martin Pool, & Dan Mosedale (But - don't send bug reports to them; report them using bugzilla, at - http://bugzilla.mozilla.org/enter_bug.cgi , project Webtools, - component Bugzilla). + don't send bug reports to them; report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla ). This document was heavily modified again Wednesday, March 07 @@ -1696,16 +1704,46 @@ exit; - Modify the invocation of all system() calls in all perl scripts in your Bugzilla directory. For instance, change this line in processmail: - -system ("./processmail.pl",@ARGLIST); - -to - + Modify the invocation of all system() calls in all perl + scripts in your Bugzilla directory. For instance, change + this line in processmail: + +system ("./processmail.pl",@ARGLIST); + to + system ("perl processmail.pl",@ARGLIST); + + + Add binmode() calls so attachments + will work (bug 62000). + + + Because Microsoft Windows based systems handle binary + files different than Unix based systems, you need to add + the following lines to + createattachment.cgi and + showattachment.cgi before the + require 'CGI.pl'; line. + + + + + + + + + According to bug 62000, the perl documentation says that you should always use binmode() when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting binmode() at the begining of the attachment files, there should be logic to determine if binmode() is needed or not. + + + @@ -1714,6 +1752,8 @@ system ("perl processmail.pl",@ARGLIST); relationships to Properties -> Home directory (tab) -> Application Settings (section) -> Configuration (button), such as: + + .cgi to: <perl install directory>\perl.exe %s %s .pl to: <perl install directory>\perl.exe %s %s @@ -1742,7 +1782,9 @@ GET,HEAD,POST registry at the following location: - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap + +HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap + The keys should be called ".pl" and ".cgi", and both @@ -1761,26 +1803,102 @@ GET,HEAD,POST If attempting to run Bugzilla 2.12 or older, you will need to remove encrypt() calls from the Perl source. This is not necessary for Bugzilla 2.13 and - later. + later, which includes the current release, Bugzilla + &bz-ver;. Removing encrypt() for Windows NT Bugzilla version 2.12 or earlier - Replace this: - -SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); -my $enteredcryptpwd = FetchOneColumn(); - - with this: - -my $enteredcryptpwd = $enteredpwd - + Replace this: + +SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); +my $enteredcryptpwd = FetchOneColumn(); + +with this: + +my $enteredcryptpwd = $enteredpwd + in cgi.pl.
+ +
+ Bugzilla LDAP Integration + + What follows is some late-breaking information on using the + LDAP authentication options with Bugzilla. The author has not + tested these (nor even formatted this section!) so please + contribute feedback to the newsgroup. + + +Mozilla::LDAP module + +The Mozilla::LDAP module allows you to use LDAP for authentication to +the Bugzilla system. This module is not required if you are not using +LDAP. + +Mozilla::LDAP (aka PerLDAP) is available for download from +http://www.mozilla.org/directory. + +NOTE: The Mozilla::LDAP module requires Netscape's Directory SDK. +Follow the link for "Directory SDK for C" on that same page to +download the SDK first. After you have installed this SDK, then +install the PerLDAP module. +---------------------------------------------------------------------- + +Post-Installation Checklist +---------------------------------------------------------------------- +Set useLDAP to "On" **only** if you will be using an LDAP directory +for authentication. Be very careful when setting up this parameter; +if you set LDAP authentication, but do not have a valid LDAP directory +set up, you will not be able to log back in to Bugzilla once you log +out. (If this happens, you can get back in by manually editing the +data/params file, and setting useLDAP back to 0.) + +If using LDAP, you must set the three additional parameters: + +Set LDAPserver to the name (and optionally port) of your LDAP server. +If no port is specified, it defaults to the default port of 389. (e.g +"ldap.mycompany.com" or "ldap.mycompany.com:1234") + +Set LDAPBaseDN to the base DN for searching for users in your LDAP +directory. (e.g. "ou=People,o=MyCompany") uids must be unique under +the DN specified here. + +Set LDAPmailattribute to the name of the attribute in your LDAP +directory which contains the primary email address. On most directory +servers available, this is "mail", but you may need to change this. +---------------------------------------------------------------------- + +(Not sure where this bit should go, but it's important that it be in +there somewhere...) +---------------------------------------------------------------------- +Using LDAP authentication for Bugzilla: + +The existing authentication scheme for Bugzilla uses email addresses +as the primary user ID, and a password to authenticate that user. All +places within Bugzilla where you need to deal with user ID (e.g +assigning a bug) use the email address. + +The LDAP authentication builds on top of this scheme, rather than +replacing it. The initial log in is done with a username and password +for the LDAP directory. This then fetches the email address from LDAP +and authenticates seamlessly in the standard Bugzilla authentication +scheme using this email address. If an account for this address +already exists in your Bugzilla system, it will log in to that +account. If no account for that email address exists, one is created +at the time of login. (In this case, Bugzilla will attempt to use the +"displayName" or "cn" attribute to determine the user's full name.) + +After authentication, all other user-related tasks are still handled +by email address, not LDAP username. You still assign bugs by email +address, query on users by email address, etc. +---------------------------------------------------------------------- + +

diff --git a/docs/sgml/integration.sgml b/docs/sgml/integration.sgml index e0547c365..36cc617e2 100644 --- a/docs/sgml/integration.sgml +++ b/docs/sgml/integration.sgml @@ -35,6 +35,14 @@ an @resolution field, you can even change the Bugzilla bug state. + + There is also a project, based upon somewhat dated Bugzilla + code, to integrate CVS and Bugzilla through CVS' ability to + email. Check it out at: + + http://homepages.kcbbs.gen.nz/~tonyg/, under the + cvszilla link. +
diff --git a/docs/sgml/patches.sgml b/docs/sgml/patches.sgml index 3a1ce90d2..3f49255f2 100644 --- a/docs/sgml/patches.sgml +++ b/docs/sgml/patches.sgml @@ -247,6 +247,104 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
+
+ Hacking Bugzilla + + What follows are some general guidelines for changing Bugzilla, and adhering to good coding practice while doing so. We've had some checkins in the past which ruined Bugzilla installations because of disregard for these conventions. Sorry for the lack of formatting; I got this info into the Guide on the day of 2.14 release and haven't formatted it yet. + + + +The following is a guide for reviewers when checking code into Bugzilla's +CVS repostory at mozilla.org. If you wish to submit patches to Bugzilla, +you should follow the rules and style conventions below. Any code that +does not adhere to these basic rules will not be added to Bugzilla's +codebase. + + 1. Usage of variables in Regular Expressions + + It is very important that you don't use a variable in a regular + expression unless that variable is supposed to contain an expression. + This especially applies when using grep. You should use: + + grep ($_ eq $value, @array); + + - NOT - + + grep (/$value/, @array); + + If you need to use a non-expression variable inside of an expression, be + sure to quote it properly (using \Q..\E). + +Coding Style for Bugzilla +------------------------- + +While it's true that not all of the code currently in Bugzilla adheres to +this styleguide, it is something that is being worked toward. Therefore, +we ask that all new code (submitted patches and new files) follow this guide +as closely as possible (if you're only changing 1 or 2 lines, you don't have +to reformat the entire file :). + + 1. Whitespace + + Bugzilla's prefered indentation is 4 spaces (no tabs, please). + + 2. Curly braces. + + The opening brace of a block should be on the same line as the statement + that is causing the block and the closing brace should be at the same + indentation level as that statement, for example: + + if ($var) { + print "The variable is true"; + } else { + print "Try again"; + } + + - NOT - + + if ($var) + { + print "The variable is true"; + } + else + { + print "Try again"; + } + + 3. File Names + + File names for bugzilla code and support documention should be legal across + multiple platforms. \ / : * ? " < > and | are all illegal characters for + filenames on various platforms. Also, file names should not have spaces in + them as they can cause confusion in CVS and other mozilla.org utilities. + + 4. Variable Names + + If a variable is scoped globally ($::variable) its name should be descriptive + of what it contains. Local variables can be named a bit looser, provided the + context makes their content obvious. For example, $ret could be used as a + staging variable for a routine's return value as the line |return $ret;| will + make it blatently obvious what the variable holds and most likely be shown + on the same screen as |my $ret = "";|. + + 5. Cross Database Compatability + + Bugzilla was originally written to work with MySQL and therefore took advantage + of some of its features that aren't contained in other RDBMS software. These + should be avoided in all new code. Examples of these features are enums and + encrypt(). + + 6. Cross Platform Compatability + + While Bugzilla was written to be used on Unix based systems (and Unix/Linux is + still the only officially supported platform) there are many who desire/need to + run Bugzilla on Microsoft Windows boxes. Whenever possible, we should strive + not to make the lives of these people any more complicated and avoid doing things + that break Bugzilla's ability to run on multiple operating systems. + + +
+ diff --git a/docs/sgml/using.sgml b/docs/sgml/using.sgml index 91a7658cd..934817081 100644 --- a/docs/sgml/using.sgml +++ b/docs/sgml/using.sgml @@ -399,13 +399,13 @@ system against which all others are measured. our Bugzilla database. Please notice the box is a scrollbox. Using the down arrow on the scrollbox, scroll down until you can see an entry - called "Webtools". Select this entry. + called "Bugzilla". Select this entry. Did you notice that some of the boxes to the right changed - when you selected "Webtools"? Every Program (or Product) + when you selected "Bugzilla"? Every Program (or Product) has different Versions, Components, and Target Milestones associated with it. A "Version" is the number of a software program. @@ -452,36 +452,67 @@ system against which all others are measured. Normally, a Component has a single Owner, who is responsible for overseeing efforts to improve that Component. - Mozilla Webtools Components + Mozilla's Bugzilla Components - Mozilla's "Webtools" Product is composed of several pieces (Components): + Mozilla's "Bugzilla" Product is composed of several pieces (Components): - Bonsai, - a tool to show recent changes to Mozilla - Bugzilla, - a defect-tracking tool - Build, - a tool to automatically compile source code - into machine-readable form - Despot, - a program that controls access to the other Webtools - LXR, - a utility that automatically marks up text files - to make them more readable - MozBot, - a "robot" that announces changes to Mozilla in Chat - TestManager, - a tool to help find bugs in Mozilla - Tinderbox, - which displays reports from Build + Administration, + Administration of a bugzilla installation, including + editcomponents.cgi, + editgroups.cgi, + editkeywords.cgi, + editparams.cgi, + editproducts.cgi, + editusers.cgi, + editversions.cgi, and + sanitycheck.cgi. + + Bugzilla-General, + Anything that doesn't fit in the other components, or spans + multiple components. + + Creating/Changing Bugs, + Creating, changing, and viewing bugs. + enter_bug.cgi, + post_bug.cgi, + show_bug.cgi and + process_bug.cgi. + + Documentation, + The bugzilla documentation, including anything in the + docs/ directory and The Bugzilla Guide + (This document :) + + Email, + Anything to do with email sent by Bugzilla. + processmail + + Installation, + The installation process of Bugzilla. This includes + checksetup.pl and whatever else it evolves into. + + Query/Buglist, + Anything to do with searching for bugs and viewing the buglists. + query.cgi and + buglist.cgi + + Reporting/Charting, + Getting reports from Bugzilla. + reports.cgi and + duplicates.cgi + + User Accounts, + Anything about managing a user account from the user's perspective. + userprefs.cgi, saved queries, creating accounts, + changing passwords, logging in, etc. + + User Interface, + General issues having to do with the user interface cosmetics (not + functionality) including cosmetic issues, HTML templates, etc. + - - A different person is responsible for each of these Components. - Tara Hernandez keeps - the "Bugzilla" component up-to-date. - diff --git a/docs/txt/Bugzilla-Guide.txt b/docs/txt/Bugzilla-Guide.txt index 46972a7d8..685ce6408 100644 --- a/docs/txt/Bugzilla-Guide.txt +++ b/docs/txt/Bugzilla-Guide.txt @@ -3,10 +3,10 @@ The Bugzilla Guide Matthew P. Barnson - barnboy@NOSPAM.trilobyte.net + barnboy@trilobyte.net Zach Lipton - zach@NOSPAM.zachlipton.com + zach AT zachlipton DOT com Revision History Revision v2.11 20 December 2000 Revised by: MPB Converted the README, FAQ, and DATABASE information into SGML docbook @@ -136,6 +136,7 @@ Matthew P. Barnson 3.6.1. Win32 Installation: Step-by-step 3.6.2. Additional Windows Tips + 3.6.3. Bugzilla LDAP Integration 4. Administering Bugzilla @@ -169,6 +170,15 @@ Matthew P. Barnson 5.4. Tinderbox/Tinderbox2 6. The Future of Bugzilla + 7. Bugzilla Variants and Competitors + + 7.1. Red Hat Bugzilla + 7.2. Loki Bugzilla (Fenris) + 7.3. Issuezilla + 7.4. Scarab + 7.5. Perforce SCM + 7.6. SourceForge + A. The Bugzilla FAQ B. Software Download Links C. The Bugzilla Database @@ -182,21 +192,13 @@ Matthew P. Barnson C.3. MySQL Permissions & Grant Tables - 7. Bugzilla Variants and Competitors - - 7.1. Red Hat Bugzilla - 7.2. Loki Bugzilla (Fenris) - 7.3. Issuezilla - 7.4. Scarab - 7.5. Perforce SCM - 7.6. SourceForge - D. Useful Patches and Utilities for Bugzilla D.1. Apache mod_rewrite magic D.2. The setperl.csh Utility D.3. Command-line Bugzilla Queries D.4. The Quicksearch Utility + D.5. Hacking Bugzilla E. GNU Free Documentation License @@ -217,7 +219,7 @@ Matthew P. Barnson List of Examples 2-1. Some Famous Software Versions - 2-2. Mozilla Webtools Components + 2-2. Mozilla's Bugzilla Components 3-1. Setting up bonsaitools symlink 3-2. Running checksetup.pl as the web user 3-3. Installing ActivePerl ppd Modules on Microsoft Windows @@ -230,6 +232,7 @@ Matthew P. Barnson 4-4. Using SortKey with Target Milestone 4-5. When to Use Group Security 4-6. Creating a New Group + 4-7. Bugzilla Groups D-1. Using Setperl to set your perl path 1. A Sample Product _________________________________________________________________ @@ -270,8 +273,8 @@ Chapter 1. About This Guide documentation. I have incorporated instructions from the Bugzilla README, Frequently Asked Questions, Database Schema Document, and various mailing lists to create it. Chances are, there are glaring - errors in this documentation; please contact - to correct them. + errors in this documentation; please contact + to correct them. _________________________________________________________________ 1.2. Copyright Information @@ -289,7 +292,7 @@ Chapter 1. About This Guide If you have any questions regarding this document, its copyright, or publishing this document in non-electronic form, please contact - Matthew P. Barnson. Remove "NOSPAM" from email address to send. + Matthew P. Barnson. _________________________________________________________________ 1.3. Disclaimer @@ -356,8 +359,8 @@ Chapter 1. About This Guide numerous e-mail and IRC support sessions, and overall excellent contribution to the Bugzilla community: - Terry Weissman for initially converting Bugzilla from BugSplat! and - writing the README upon which this documentation is largely based. + Terry Weissman for initially writing Bugzilla and creating the README + upon which the UNIX installation documentation is largely based. Tara Hernandez for keeping Bugzilla development going strong after Terry left Mozilla.org @@ -380,7 +383,7 @@ Chapter 1. About This Guide documentation (in no particular order): Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron - Teitelbaum + Teitelbaum, Jacob Steenhagen, Joe Robins _________________________________________________________________ 1.7. Feedback @@ -686,10 +689,10 @@ Chapter 2. Using Bugzilla can narrow our search down to only specific products (software programs or product lines) in our Bugzilla database. Please notice the box is a scrollbox. Using the down arrow on the scrollbox, - scroll down until you can see an entry called "Webtools". Select + scroll down until you can see an entry called "Bugzilla". Select this entry. 4. Did you notice that some of the boxes to the right changed when - you selected "Webtools"? Every Program (or Product) has different + you selected "Bugzilla"? Every Program (or Product) has different Versions, Components, and Target Milestones associated with it. A "Version" is the number of a software program. Example 2-1. Some Famous Software Versions @@ -715,22 +718,33 @@ Chapter 2. Using Bugzilla program, or some other logical division of a Product or Program. Normally, a Component has a single Owner, who is responsible for overseeing efforts to improve that Component. - Example 2-2. Mozilla Webtools Components - Mozilla's "Webtools" Product is composed of several pieces + Example 2-2. Mozilla's Bugzilla Components + Mozilla's "Bugzilla" Product is composed of several pieces (Components): - Bonsai, a tool to show recent changes to Mozilla - Bugzilla, a defect-tracking tool - Build, a tool to automatically compile source code into - machine-readable form - Despot, a program that controls access to the other Webtools - LXR, a utility that automatically marks up text files to make them - more readable - MozBot, a "robot" that announces changes to Mozilla in Chat - TestManager, a tool to help find bugs in Mozilla - Tinderbox, which displays reports from Build - A different person is responsible for each of these Components. - Tara Hernandez keeps the "Bugzilla" component up-to-date. + Administration, Administration of a bugzilla installation, including + editcomponents.cgi, editgroups.cgi, editkeywords.cgi, editparams.cgi, + editproducts.cgi, editusers.cgi, editversions.cgi, and + sanitycheck.cgi. + Bugzilla-General, Anything that doesn't fit in the other components, + or spans multiple components. + Creating/Changing Bugs, Creating, changing, and viewing bugs. + enter_bug.cgi, post_bug.cgi, show_bug.cgi and process_bug.cgi. + Documentation, The bugzilla documentation, including anything in the + docs/ directory and The Bugzilla Guide (This document :) + Email, Anything to do with email sent by Bugzilla. processmail + Installation, The installation process of Bugzilla. This includes + checksetup.pl and whatever else it evolves into. + Query/Buglist, Anything to do with searching for bugs and viewing the + buglists. query.cgi and buglist.cgi + Reporting/Charting, Getting reports from Bugzilla. reports.cgi and + duplicates.cgi + User Accounts, Anything about managing a user account from the user's + perspective. userprefs.cgi, saved queries, creating accounts, changing + passwords, logging in, etc. + User Interface, General issues having to do with the user interface + cosmetics (not functionality) including cosmetic issues, HTML + templates, etc. A "Milestone", or "Target Milestone" is a often a planned future "Version" of a product. In many cases, though, Milestones simply represent significant dates for a developer. Having certain @@ -1439,6 +1453,12 @@ bash# mkdir /usr/bonsaitools bash# mkdir /usr/bonsaitools/bin bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl + Alternately, you can simply run this perl one-liner to change your + path to perl in all the files in your Bugzilla installation: +perl -pi -e 's@#!/usr/bonsaitools/bin/perl@/usr/bin/perl@' *cgi *pl Bug.pm + + Change the second path to perl to match your installation. + Tip If you don't have root access to set this symlink up, check out the @@ -1853,8 +1873,7 @@ bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \ , with some edits by Terry Weissman, Bryce Nesbitt, Martin Pool, & Dan Mosedale (But don't send bug reports to them; report them using bugzilla, at - http://bugzilla.mozilla.org/enter_bug.cgi , project Webtools, - component Bugzilla). + http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla ). This document was heavily modified again Wednesday, March 07 2001 to reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The @@ -2104,20 +2123,40 @@ exit; your Bugzilla directory. For instance, change this line in processmail: + system ("./processmail.pl",@ARGLIST); to + system ("perl processmail.pl",@ARGLIST); + 14. Add binmode() calls so attachments will work (bug 62000). + Because Microsoft Windows based systems handle binary files + different than Unix based systems, you need to add the following + lines to createattachment.cgi and showattachment.cgi before the + require 'CGI.pl'; line. + +binmode(STDIN); +binmode(STDOUT); + + Note + + According to bug 62000, the perl documentation says that you should + always use binmode() when dealing with binary files, but never when + dealing with text files. That seems to suggest that rather than + aribtrarily putting binmode() at the begining of the attachment files, + there should be logic to determine if binmode() is needed or not. + Tip If you are using IIS or Personal Web Server, you must add cgi relationships to Properties -> Home directory (tab) -> Application Settings (section) -> Configuration (button), such as: + .cgi to: \perl.exe %s %s .pl to: \perl.exe %s %s GET,HEAD,POST @@ -2139,8 +2178,7 @@ GET,HEAD,POST Basically you need to add two String Keys in the registry at the following location: - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Paramete - rs\ScriptMap +HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap The keys should be called ".pl" and ".cgi", and both should have a value something like: c:/perl/bin/perl.exe "%s" "%s" @@ -2152,14 +2190,15 @@ GET,HEAD,POST If attempting to run Bugzilla 2.12 or older, you will need to remove encrypt() calls from the Perl source. This is not necessary for - Bugzilla 2.13 and later. + Bugzilla 2.13 and later, which includes the current release, Bugzilla + 2.14. Example 3-4. Removing encrypt() for Windows NT Bugzilla version 2.12 or earlier Replace this: -SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SqlQuote(substr($rea +SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($rea lcryptpwd, 0, 2)) . ")"); my $enteredcryptpwd = FetchOneColumn(); @@ -2170,6 +2209,66 @@ my $enteredcryptpwd = $enteredpwd in cgi.pl. _________________________________________________________________ +3.6.3. Bugzilla LDAP Integration + + What follows is some late-breaking information on using the LDAP + authentication options with Bugzilla. The author has not tested these + (nor even formatted this section!) so please contribute feedback to + the newsgroup. + + Mozilla::LDAP module + The Mozilla::LDAP module allows you to use LDAP for authentication to + the Bugzilla system. This module is not required if you are not using + LDAP. + Mozilla::LDAP (aka PerLDAP) is available for download from + http://www.mozilla.org/directory. + NOTE: The Mozilla::LDAP module requires Netscape's Directory SDK. + Follow the link for "Directory SDK for C" on that same page to + download the SDK first. After you have installed this SDK, then + install the PerLDAP module. + ---------------------------------------------------------------------- + Post-Installation Checklist + ---------------------------------------------------------------------- + Set useLDAP to "On" **only** if you will be using an LDAP directory + for authentication. Be very careful when setting up this parameter; + if you set LDAP authentication, but do not have a valid LDAP directory + set up, you will not be able to log back in to Bugzilla once you log + out. (If this happens, you can get back in by manually editing the + data/params file, and setting useLDAP back to 0.) + If using LDAP, you must set the three additional parameters: + Set LDAPserver to the name (and optionally port) of your LDAP server. + If no port is specified, it defaults to the default port of 389. (e.g + "ldap.mycompany.com" or "ldap.mycompany.com:1234") + Set LDAPBaseDN to the base DN for searching for users in your LDAP + directory. (e.g. "ou=People,o=MyCompany") uids must be unique under + the DN specified here. + Set LDAPmailattribute to the name of the attribute in your LDAP + directory which contains the primary email address. On most directory + servers available, this is "mail", but you may need to change this. + ---------------------------------------------------------------------- + (Not sure where this bit should go, but it's important that it be in + there somewhere...) + ---------------------------------------------------------------------- + Using LDAP authentication for Bugzilla: + The existing authentication scheme for Bugzilla uses email addresses + as the primary user ID, and a password to authenticate that user. All + places within Bugzilla where you need to deal with user ID (e.g + assigning a bug) use the email address. + The LDAP authentication builds on top of this scheme, rather than + replacing it. The initial log in is done with a username and password + for the LDAP directory. This then fetches the email address from LDAP + and authenticates seamlessly in the standard Bugzilla authentication + scheme using this email address. If an account for this address + already exists in your Bugzilla system, it will log in to that + account. If no account for that email address exists, one is created + at the time of login. (In this case, Bugzilla will attempt to use the + "displayName" or "cn" attribute to determine the user's full name.) + After authentication, all other user-related tasks are still handled + by email address, not LDAP username. You still assign bugs by email + address, query on users by email address, etc. + ---------------------------------------------------------------------- + _________________________________________________________________ + Chapter 4. Administering Bugzilla Or, I just got this cool thing installed. Now what the heck do I do @@ -2880,6 +2979,84 @@ Chapter 4. Administering Bugzilla instructions for creating a new Product. If you need to add users to these new groups as you create them, you will find the option to add them to the group available under the "Edit User" screens. + + You may find this example illustrative for how bug groups work. + + Example 4-7. Bugzilla Groups + + Bugzilla Groups example + ----------------------- + For this example, let us suppose we have four groups, call them + Group1, Group2, Group3, and Group4. + We have 5 users, User1, User2, User3, User4, User5. + We have 8 bugs, Bug1, ..., Bug8. + Group membership is defined by this chart: + (X denotes that user is in that group.) + (I apologize for the nasty formatting of this table. Try viewing + it in a text-based browser or something for now. -MPB) + G G G G + r r r r + o o o o + u u u u + p p p p + 1 2 3 4 + +-+-+-+-+ + User1|X| | | | + +-+-+-+-+ + User2| |X| | | + +-+-+-+-+ + User3|X| |X| | + +-+-+-+-+ + User4|X|X|X| | + +-+-+-+-+ + User5| | | | | + +-+-+-+-+ + Bug restrictions are defined by this chart: + (X denotes that bug is restricted to that group.) + G G G G + r r r r + o o o o + u u u u + p p p p + 1 2 3 4 + +-+-+-+-+ + Bug1| | | | | + +-+-+-+-+ + Bug2| |X| | | + +-+-+-+-+ + Bug3| | |X| | + +-+-+-+-+ + Bug4| | | |X| + +-+-+-+-+ + Bug5|X|X| | | + +-+-+-+-+ + Bug6|X| |X| | + +-+-+-+-+ + Bug7|X|X|X| | + +-+-+-+-+ + Bug8|X|X|X|X| + +-+-+-+-+ + Who can see each bug? + Bug1 has no group restrictions. Therefore, Bug1 can be seen by any + user, whatever their group membership. This is going to be the only + bug that User5 can see, because User5 isn't in any groups. + Bug2 can be seen by anyone in Group2, that is User2 and User4. + Bug3 can be seen by anyone in Group3, that is User3 and User4. + Bug4 can be seen by anyone in Group4. Nobody is in Group4, so none of + these users can see Bug4. + Bug5 can be seen by anyone who is in _both_ Group1 and Group2. This + is only User4. User1 cannot see it because he is not in Group2, and + User2 cannot see it because she is not in Group1. + Bug6 can be seen by anyone who is in both Group1 and Group3. This + would include User3 and User4. Similar to Bug5, User1 cannot see Bug6 + because he is not in Group3. + Bug7 can be seen by anyone who is in Group1, Group2, and Group3. This + is only User4. All of the others are missing at least one of those + group priveleges, and thus cannot see the bug. + Bug8 can be seen by anyone who is in Group1, Group2, Group3, and + Group4. There is nobody in all four of these groups, so nobody can + see Bug8. It doesn't matter that User4 is in Group1, Group2, and + Group3, since he isn't in Group4. _________________________________________________________________ 4.4. Bugzilla Security @@ -3012,6 +3189,10 @@ Chapter 5. Integrating Bugzilla with Third-Party Tools have CVS check-in comments append to your Bugzilla bug. If you have your check-in script include an @resolution field, you can even change the Bugzilla bug state. + + There is also a project, based upon somewhat dated Bugzilla code, to + integrate CVS and Bugzilla through CVS' ability to email. Check it out + at: http://homepages.kcbbs.gen.nz/~tonyg/, under the "cvszilla" link. _________________________________________________________________ 5.3. Perforce SCM @@ -3039,10 +3220,665 @@ Chapter 6. The Future of Bugzilla Bugzilla's Future. Much of this is the present, now. - The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do not have - more information about it right now, and most of what went into the - "future" section is now present. That stuff was blue-sky a year ago; - MattyT should have me a new document sometime... + Bugzilla's future is a constantly-changing thing, as various + developers "scratch an itch" when it comes to functionality. Thus this + section is very malleable, subject to change without notice, etc. + You'll probably also notice the lack of formatting. I apologize that + it's not quite as readable as the rest of the Guide. + + Bugzilla Blue Sky + Customisability + One of the major stumbling blocks of Bugzilla has been that it is t + oo + rigid and does not adapt itself well enough to the needs of an + organisation. This has led to organisations making changes to the + Bugzilla code that need to be redone each new version of Bugzilla. + Bugzilla should attempt to move away from this to a world where thi + s + doesn't need to occur. + Most of the subsections in this section are currently explicit desi + gn + goals for the "Bugzilla 3" rewrite. This does not necessarily mean + that they will not occur before them in Bugzilla 2, but most are + significant undertakings. + Field Customisation + Many installations wish to customise the fields that appear on bug + reports. Current versions of Bugzilla offer limited + customisability. In particular, some fields can be turned off. + However, many administrators wish to add their own fields, and rena + me + or otherwise modify existing fields. An architecture that supports + this would be extraordinarily useful. + Indeed, many fields work similarly and could be abstracted into "fi + eld + types", so that an administrator need write little or no code to + support the new fields they desire. + Possible field types include text (eg status whiteboard), numbers, + dates (eg report time), accounts (eg reporter, qa, cc), inter-bug + relationships (dependencies, duplicates), option groups (platform, + os, + severity, priority, target milestone, version) etc. + Ideally an administrator could configure their fields through a + Bugzilla interface that requires no code to be added. However, it + is + highly unlikely this ideal will never be met, and in a similar way + that office applications have scripting languages, Bugzilla should + allow new field types to be written. + Similarly, a common desire is for resolutions to be added or remove + d. + Allocations + ? + Option Groups + ? + Relations + ? + Database Integrity + Furthermore, it is desirable for administrators to be able to speci + fy + rules that must or should apply between the fields on a bug report. + For example, you might wish to specify that a bug with status ASSIG + NED + must have a target milestone field that that is not untargetted. O + r + that a bug with a certain number of votes should get ASSIGNED. Or + that the QA contact must be different from the assignee. + "Must" relationships could be implemented by refusing to make chang + es + that violate the relationships, or alternatively, automatically + updating certain fields in order to satisfy the criteria. Which + occurs should be up to the administrator. + "Should" relationships could be implemented by a combination of + emitting warnings on the process bug page, the same on notification + mails, or emitting periodic whine mails about the situation. Again + , + which occurs should be up to the administrator. + It should also be possible for whine mails to be emitted for "must" + relationships, as they might become violated through direct databas + e + access, Bugzilla bugs, or because they were there before the + relationship was enforced. + As well as implementing intra-bug constraints, it would be useful t + o + create inter-bug constraints. For example, a bug that is dependent + on + another bug should not have an earlier milestone or greater priorit + y + than that bug. + Database Adaptability + Often an administrator desires that fields adapt to the values of + other fields. For example, the value of a field might determine th + e + possible values of another field or even whether it appears (whethe + r + it is "applicable"). + Limited adaptability is present in Bugzilla 2, and only on the + "Product" field: + * The possible values of the target milestone, version and compon + ent + fields depend on the product. + * UNCONFIRMED can be turned off for specific products. + * Voting can be configured differently or turned off for differen + t + products, and there is a separate user vote limits for each + product. + It would be good if more adaptability was present, both in terms of + all fields relying on the product, as well as the ability to adapt + based on the value of all fields. + Example ??? + General adaptability raises the issue of circular references betwee + n + fields causing problems. One possible solution to this is to place + the fields in a total ordering and require a field refer only to th + e + previous fields. + In Bugzilla 2, changing the product of a bug meant a second page wo + uld + appear that allowed you to choose a new milestone, component and + version, as those fields adapted themselves to the new product. Th + is + page could be generalised to support all instances where: + * a field value must or might be changed because the possible val + ues + have changed + * is going to drop off because it it is no longer applicable, and + this should be confirmed + * must be specified because it is suddenly applicable, and the + default value, if one exists, might not be acceptable + Database Independence + Currently Bugzilla only runs on the MySQL database. It would be + desirable for Bugzilla to run on other databases, because: + * Organisations may have existing database products they use and + would prefer to run a homogenous environment. + * Databases each have their own shortcomings, including MySQL. A + n + administrator might choose a database that would work better wi + th + their Bugzilla. + This raises the possibility that we could use features that are onl + y + present in some databases, by appropriately falling back. For + example, in the MySQL world, we live without: + * record-level locking, instead we use table-level locking + * referential and record constraints, instead we checking code + * subselects, instead we use multiple queries and redundant "cach + es" + Multiple Front Ends + Currently Bugzilla is manipulated via the Web, and notifies via + E-Mail. It would be desirable for Bugzilla to easily support vario + us + front ends. + There is no reason that Bugzilla could not be controlled via a whol + e + range of front ends, including Web, E-Mail, IRC, ICQ, etc, and + similarly for how it notifies. It's also possible that we could + introduce a special Bugzilla client that uses its own protocol, for + maximum user productivity. + Indeed a request reply might be returned via a totally different + transport method than was use to submit the request. + Internationalisation + Bugzilla currently supports only English. All of the field names, + user instructions, etc are written in English. It would be desirab + le + to allow "language packs" so Bugzilla can be easily used in + non-English speaking locales. + To a degree field customisation supports this, because administrato + rs + could specify their own fields names anyway. However, there will + always be some basic facilities not covered by this, and it is + desirable that the administrator's interface also is + internationalisable. + Better Searching + General Summary Reports + Sometimes, the normal querying page leaves a lot to be desired. Th + ere + are other facilities already in place or which people have asked fo + r: + Most Doomed Reports - All Bugs or All Bugs In A Product, Categorise + d + On Assignee, Shows and Counts Number of Bugs For Each Assignee + Most Voted For Bugs - All Bugs, Categorised On Product, Shows Top T + en + Bugs Voters Most Want Fixed + Number of Open Bugs For An Assignee - Bug List, Categorised On + Developers, Counts Number of Bugs In Category + The important thing to realise is that people want categorised repo + rts + on all sorts of things - a general summary report. + In a categorised report, you choose the subset of bugs you wish to + operate on (similar to how you would specify a query), and then + categorise them on one or more fields. + For each category you display the count of the number of things in + that category. You can optionally display the bugs themselves, or + leave them out, just showing the counts. And you can optionally li + mit + the number of things (bugs or subcategories) that display in each + category. + Such a mechanism would let you do all of the above and more. + Applications of this mechanism would only be recognised once it was + implemented. + Related Bugs + It would be nice to have a field where you could enter other bugs + related to the current bug. It would be handy for navigation and + possibly even finding duplicates. + Column Specification Support + Currently bug lists use the columns that you last used. This doesn + 't + work well for "prepackaged queries", where you followed a link. Yo + u + can probably add a column by specifying a sort column, but this is + difficult and suboptimal. + Furthermore, I find that when I want to add a column to a bug list, + it's usually a one off and I would prefer it to go away for the nex + t + query. Hence, it would be nice to specify the columns that appear + on + the bug list (and general summary report) pages. The default query + mechanism should be able to let you specify your default columns. + Advanced Querying Redesign + ? + Keywords + People have a need to apply tags to bugs. In the beginning, people + placed designators in the summary and status whiteboard. However, + these fields were not designed for that, and so there were many fla + ws + with this system: + * They pollute the field with information that was never intended + to + be present. + * Removing them with a bulk change is a difficult problem that ha + s + too many pitfalls to implement. + * You can easily get the capitalisation wrong. + Then dependencies were introduced (when?), and people realised that + they could use them for "tracking bugs". Again, dependencies were + not + designed for that, and so there were more flaws, albeit different + ones, including: + * They aren't really bugs, so it's difficult to distinguish issue + s + from bugs. + * They can pollute bugs counts, and you must somehow exclude them + from queries. + * There is a whole lot of useless information on them. They have + an + assignee but there is nothing to fix, and that person can get + whined at by Bugzilla. They have target milestones which must + be + manually maintained. And so on. + Finally, keywords were introduced (when?) for this purpose to remov + e + the need for these two systems. Unfortunately, the simple keywords + implementation was itself lacking in certain features provided by t + he + two previous systems, and has remained almost unchanged since its + inception. Furthermore, it could not be forseen that in large + installations, the sheer number of keywords could become unwieldly + and + could lead to a movement back to the other systems. + The keywords system was the right idea, however, and it remains so. + Fixing the keywords system is one of the most important Bugzilla + issues. + Bringing Keywords Up To Par + For the most part, keywords are very good at what they do. It is e + asy + to add and remove them (unlike summary/whiteboard designators), we + can + simply see what issues are present on a bug (unlike tracking bugs), + and we do not confuse bugs with issues (unlike tracking bugs). + However, there are still some "regressions" in the keyword system o + ver + previous systems: + * Users wish to view the "dependency forest" of a keyword. While + a + dependency tree is of one bug, a dependency forest is of a bug + list, and consists of a dependency tree for each member of the + bug + list. Users can work around this with tracking bugs by creatin + g a + tracking bug and viewing the dependency tree of that tracking b + ug. + * Users wish to specify the keywords that initially apply to a bu + g, + but instead they must edit the bug once it has already been + submitted. They can work around this with summary designators, + since they specify the summary at reporting time. + * Users wish to store or share a bug list that contains a keyword + s + column. Hence they wish to be able to specify what columns app + ear + in the bug list URL, as mentioned earlier. They can work aroun + d + this using summary designators, since almost all bug lists have + a + summary column. + * Users wish to be able to view keywords on a bug list. However + often they are only interested in a small number of keywords. + Having a bug list with a keywords column means that all keyword + s + will appear on a bug list. This can take a substantial amount + of + space where a bug has a lot of keywords, since the table column + s + in Bugzilla adjust to the largest cell in that column. Hence + users wish to be able to specify which keywords should appear i + n + the bug list. In a very real sense, each keyword is a field un + to + itself. Users can work around this by using summary designator + s, + since they keywords will share the space in the summary column. + * Users wish to know when bugs with a specific issue are resolved + . + Hence they wish to be able to receive notifications on all the + bugs with a specific keyword. The introduction a generic watch + ing + facility (also for things like watching all bugs in a component + ) + would achieve this. Users can work around this by using tracki + ng + bugs, as dependencies have an existing way of detecting fixes t + o + bug a bug was blocked by. + Dealing With The Keyword Overload + At the time of writing, the mozilla.org installation has approximat + ely + 100 keywords, and many more would be in use if the keywords system + didn't have the problems it does. + Such a large number of keywords introduces logistical problems: + * It must be easy for someone to learn what a keyword means. If + a + keyword is buried within a lot of other keywords, it can be + difficult to find. + * It must be easy to see what keywords are on a bug. If the numb + er + of keywords is large, then this can be difficult. + These lead some people to feel that there are "too many keywords". + These problems are not without solutions however. It is harder to + find a list of designators or tracking bugs than it is a list of + keywords. + The essential problem is it needs to be easy to find the keywords + we're interested in through the mass of keywords. + Keyword Applicability + As has been previously mentioned, it is desirable for fields to be + able to adapt to the values of other fields. This is certainly tru + e + for keywords. Many keywords are simply not relevant because of the + bugs product, component, etc. + Hence, by introducing keyword applicability, and not displaying + keywords that are not relevant to the current bug, or clearly + separating them, we can make the keyword overload problem less + significant. + Currently when you click on "keywords" on a bug, you get a list of + all + bugs. It would be desirable to introduce a list of keywords tailor + ed + to a specific bug, that reports, in order: + * the keywords currently on the bug + * the keywords not currently on the bug, but applicable to the bu + g + * optionally, the keywords not applicable to the bug + This essentially orders the keywords into three groups, where each + group is more important than the previous, and therefore appears + closer to the top. + Keyword Grouping & Ordering + We could further enhance both the global and bug specific keyword l + ist + by grouping keywords. We should always have a "flat" view of + keywords, but other ways of viewing the keywords would be useful to + o. + If keyword applicability was implemented, we could group keywords + based on their "applicability condition". Keywords that apply to a + ll + bugs could be separated from keywords that apply to a specific + product, both on the global keyword list and the keyword list of a + bug + that is in that product. + We could specify groups of our own. For example, many keywords are + in + a mutually exclusive group, essentially like radio buttons in a use + r + interface. This creates a natural grouping, although other groupin + gs + occur (which depends on your keywords). + It is possible that we could use collapsing/expanding operations on + "twisties" to only should the groups we are interested in. + And instead of grouping keywords, we could order them on some metri + c + of usefulness, such as: + * when the keyword was last added to a bug + * how many bugs the keyword is on + * how many open bugs the keyword is on + Opting Out Of Keywords + Not all people are going to care about all keywords. Therefore it + makes sense that you may wish to specify which keywords you are + interested in, either on the bug page, or on notifications. + Other keywords will therefore not bother users who are not interest + ed + in them. + Keyword Security + Currently all keywords are available and editable to all people wit + h + edit bugs access. This situation is clearly suboptimal. + Although relying on good behaviour for people to not do what they + shouldn't works reasonably well on the mozilla.org, it is better to + enforce that behaviour - it can be breached through malice, acciden + t + or ignorance. + And in the situation where it is desirable for the presence or abse + nce + of a keyword not to be revealed, organisations either need to be + content with the divulgence, or not use keywords at all. + In the situation where they choose to divulge, introducing the abil + ity + to restrict who can see the keyword would also reduce keyword + overload. + Personal Keywords + Keywords join together a set of bugs which would otherwise be + unrelated in the bug system. + We allow users to store their own queries. However we don't allow + them to store their own keywords on a bug. This reduces the + usefulness of personal queries, since you cannot join a set of + unrelated bugs together in a way that you wish. Lists of bug numbe + rs + can work, by they can only be used for small lists, and it is + impossible to share a list between multiple queries. + Personal keywords are necessary to replace personal tracking bugs, + as + they would not pollute the keyword space. Indeed, on many + installations this could remove some keywords out of the global + keyword space. + In a similar vein and with similar effects, group keywords could be + introduced that are only available to members of a specific group. + Keyword Restrictions + Keywords are not islands unto themselves. Along with their potenti + al + to be involved in the inter-field relationships mentioned earlier, + keywords can also be related to other keywords. + Essentially, there are two possibilities: + * a set of keywords are mutually exclusive + * the presence of a keyword implies another keyword must be prese + nt + Introduction of the ability to specify these restrictions would hav + e + benefits. + If mutually exclusive keywords were present on a bug, their removal + would fix up the database, as well as reducing the number of keywor + ds + on that bug. + In the situation where a keyword implies another keyword, there are + two possiblities as to how to handle the situation. + The first is automatically add the keyword. This would fix up the + database, but it would increase the number of keywords on a bug. + The second is to automatically remove the keyword, and alter querie + s + so they pick up the first keyword as well as the removed keyword. + This would fix up the database and reduce the number of keywords on + a + bug, but it might confuse users who don't see the keyword. + Alternatively, the implied keywords could be listed separately. + Notifications + Every time a bug gets changed notifications get sent out to people + letting them know about what changes have been made. This is a + significant feature, and all sorts of questions can be raised, but + they mainly boil down to when they should be sent and what they sho + uld + look like. + Changes You're Interested In + As of version 2.12 users can specify what sort of changes they are + interested in receiving notifications for. However, this is still + limited. As yet there is no facility to specify which keywords you + care about, and whether you care about changes to fields such as th + e + QA contact changes. + Furthermore, often an unnecessary comment will go along with a chan + ge, + either because it is required, or the commenter is ignorant of how + the + new system works. While explaining why you did something is useful + , + merely commenting on what you did is not because that information i + s + already accessible view "Bug Activity". + Because of this unnecessary comment, a lot of changes that would + otherwise not generate notifications for certain people do so, beca + use + few people are willing to turn off comments. One way to deal with + this problem is to allow people to specify that their comments are + purely explanatory, and that anyone who is not interested in the + change will not be interested in the comment. + Furthermore, one possible rationale for unnecessary comments is tha + t + the bug activity does not display on the normal page and hence it i + s + difficult to cross reference comments and actions. Hence, it would + be + beneficial to be able to do this. + Bugs You're Watching + Currently to receive a notification about a bug you need to have yo + ur + name on it. This is suboptimal because you need to know about a bu + g + before you can receive notifications on it. Often you are interest + ed + in any bug with a field set to a specific value. For example, you + might be interested in all bugs with a specific product, component + or + keyword. + If someone could automatically receive notifications about these bu + gs, + it would make everyone's lives easier. Currently the default assig + nee + and QA contact for a component will automatically receive + notifications for + Question: This moves half way to a BCC. + Bulk Changes + A very useful feature of Bugzilla is the ability to perform an acti + on + on multiple bugs at once. However, this means that similar + notifications are currently generated for each bug modified. + This can result in a torrent of notifications that can annoy. + Furthermore, since the bugs are all changed close to each other in + time, it is easy for someone to mass delete all the notifications + generated by a bulk change and miss an unrelated notification in th + e + middle. + These factors can lead to a tendency for people to delay bulk chang + es, + or avoid them entirely. This is suboptimal. + It would be better if a bulk change generated only one notification + mail. This would vastly reduce the annoyance factor, and prevent + accidental deletion of notifications. + One problem with this change is that some people separate out + notifications using filtering. This means that they would no longe + r + be match parts of a bulk change under different filtering rules. + One possibility to resolve this is to allow people to specify group + s + of bugs. All bugs within a group would go into the same + notification. The filters could then distinguish the different bug + groups. + In any case, it is likely there would need to be a transition perio + d + to allow people to alter their filters. + Nominations + ? + Linking Bugzilla Installations + The first example of linking Bugzilla installations together has is + the introduction of bug moving in version 2.12. However, it would + be + useful to be able to link installations in more ways. + * Dependencies and other relationships between bugs in other + installations. This is difficult because dependencies are + synchronised on both bugs, so the installation that changes + dependencies would need to communicate the new state to the oth + er + installation. It would also mean that relationships and + notifications that refer to other bugs would need to communicat + e + with the other installation. + * References to bugs in other installations. Currently if you ty + pe + "bug XXX" or "bug #XXX" where XXX is a number, you get an + automatic hyperlink to that bug. It would be useful if you cou + ld + say "YYY bug #XXX" where YYY is the name of another installatio + n. + Retirement + ? + Whiny Reports + ? + Group Redesign + ? + Hard Wrapping Comments + Currently Bugzilla "hard wraps" its comments to a specific line siz + e, + similar to E-Mail. This has various problems: + * The way it currently works, wrapping is done in the browser at + submission time using a non-standard HTML extension not support + ed + by some (uncommon) browsers. These browsers generate comments + that scroll off the right side of the screen. + * Because comments are of fixed width, when you expand your brows + er + window, the comments do not expand to fit available space. + It would be much better to move to a world of soft wrapping, where + the + browser wraps the text at display time, similar to a world processo + r. + And as in a word processor, soft wrapping does not preclude the + insertion of newlines. + Hard wrapping is too entrenched into text E-Mail to fix, but we can + fix Bugzilla without causing any problems. The old content will st + ill + be wrapped too early, but at least new content will work. + _________________________________________________________________ + +Chapter 7. Bugzilla Variants and Competitors + + I created this section to answer questions about Bugzilla competitors + and variants, then found a wonderful site which covers an awful lot of + what I wanted to discuss. Rather than quote it in its entirety, I'll + simply refer you here: http://linas.org/linux/pm.html + _________________________________________________________________ + +7.1. Red Hat Bugzilla + + Red Hat Bugzilla is probably the most popular Bugzilla variant on the + planet. One of the major benefits of Red Hat Bugzilla is the ability + to work with Oracle, MySQL, and PostGreSQL databases serving as the + back-end, instead of just MySQL. Dave Lawrence has worked very hard to + keep Red Hat Bugzilla up-to-date, and many people prefer the + snappier-looking page layout of Red Hat Bugzilla to the default + Mozilla-standard formatting. + + URL: http://bugzilla.redhat.com/bugzilla/ + _________________________________________________________________ + +7.2. Loki Bugzilla (Fenris) + + Fenris can be found at http://fenris.lokigames.com. It is a fork from + Bugzilla. + _________________________________________________________________ + +7.3. Issuezilla + + Issuezilla is another fork from Bugzilla, and seems nearly as popular + as the Red Hat Bugzilla fork. Some Issuezilla team members are regular + contributors to the Bugzilla mailing list/newsgroup. Issuezilla is not + the primary focus of bug-tracking at tigris.org, however. Their + Java-based bug-tracker, Scarab, a newfangled Java-based issue tracker, + is under heavy development and looks promising! + + URL: http://issuezilla.tigris.org/servlets/ProjectHome + _________________________________________________________________ + +7.4. Scarab + + Scarab is a promising new bug-tracking system built using Java Serlet + technology. As of this writing, no source code has been released as a + package, but you can obtain the code from CVS. + + URL: http://scarab.tigris.org + _________________________________________________________________ + +7.5. Perforce SCM + + Although Perforce isn't really a bug tracker, it can be used as such + through the "jobs" functionality. + + http://www.perforce.com/perforce/technotes/note052.htmlhttp://www.perf + orce.com/perforce/technotes/note052.html + _________________________________________________________________ + +7.6. SourceForge + + SourceForge is more of a way of coordinating geographically + distributed free software and open source projects over the Internet + than strictly a bug tracker, but if you're hunting for bug-tracking + for your open project, it may be just what the software engineer + ordered! + + URL: http://www.sourceforge.net _________________________________________________________________ Appendix A. The Bugzilla FAQ @@ -3130,51 +3966,47 @@ Appendix A. The Bugzilla FAQ fields? If I wanted to take the results of a query and export that data to MS Excel, could I do that? - A.4.14. Does Bugzilla allow fields to be added, changed or - deleted? If I want to customize the bug submission form - to meet our needs, can I do that using our terminology? - - A.4.15. Has anyone converted Bugzilla to another language to be + A.4.14. Has anyone converted Bugzilla to another language to be used in other countries? Is it localizable? - A.4.16. Can a user create and save reports? Can they do this in + A.4.15. Can a user create and save reports? Can they do this in Word format? Excel format? - A.4.17. Can a user re-run a report with a new project, same + A.4.16. Can a user re-run a report with a new project, same query? - A.4.18. Can a user modify an existing report and then save it + A.4.17. Can a user modify an existing report and then save it into another name? - A.4.19. Does Bugzilla have the ability to search by word, phrase, + A.4.18. Does Bugzilla have the ability to search by word, phrase, compound search? - A.4.20. Can the admin person establish separate group and + A.4.19. Can the admin person establish separate group and individual user privileges? - A.4.21. Does Bugzilla provide record locking when there is + A.4.20. Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use or how are they notified? - A.4.22. Are there any backup features provided? - A.4.23. Can users be on the system while a backup is in progress? + A.4.21. Are there any backup features provided? + A.4.22. Can users be on the system while a backup is in progress? - A.4.24. What type of human resources are needed to be on staff to + A.4.23. What type of human resources are needed to be on staff to install and maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of individuals would we need to hire and how much would that cost vs buying an "Out-of-the-Box" solution. - A.4.25. What time frame are we looking at if we decide to hire + A.4.24. What time frame are we looking at if we decide to hire people to install and maintain the Bugzilla? Is this something that takes hours or weeks to install and a couple of hours per week to maintain and customize or is this a multi-week install process, plus a full time job for 1 person, 2 people, etc? - A.4.26. Is there any licensing fee or other fees for using + A.4.25. Is there any licensing fee or other fees for using Bugzilla? Any out-of-pocket cost other than the bodies needed as identified above? @@ -3645,51 +4477,50 @@ Appendix A. The Bugzilla FAQ progression states, also require adjusting the program logic to compensate for the change. + There is no GUI for adding fields to Bugzilla at this time. You can + follow development of this feature at + http://bugzilla.mozilla.org/show_bug.cgi?id=91037 + A.4.7. The index.html page doesn't show the footer. It's really annoying to have to go to the querypage just to check my "my bugs" link. How do I get a footer on static HTML pages? - This was a late-breaking question for the Guide, so I just have to - quote the relevant newsgroup thread on it. + It's possible to get the footer on the static index page using Server + Side Includes (SSI). The trick to doing this is making sure that your + web server is set up to allow SSI and specifically, the #exec + directive. You should also rename index.html to index.shtml. - > AFAIK, most sites (even if they have SSI enabled) won't have #exec c - md - > enabled. Perhaps what would be better is a #include virtual and a - > footer.cgi the basically has the "require 'CGI.pl' and PutFooter com - mand. - > - > Please note that under most configurations, this also requires namin - g - > the file from index.html to index.shtml (and making sure that it wil - l - > still be reconized as an index). Personally, I think this is better - on - > a per-installation basis (perhaps add something to the FAQ that says - how - > to do this). - Good point. Yeah, easy enough to do, that it shouldn't be a big deal - for - someone to take it on if they want it. FAQ is a good place for it. - > Dave Miller wrote: - > - >> I did a little experimenting with getting the command menu and foot - er on - >> the end of the index page while leaving it as an HTML file... - >> - >> I was successful. :) - >> - >> I added this line: - >> - >> - >> - >> Just before the at the end of the file. And it wor - ked. - >> - >> Thought I'd toss that out there. Should I check this in? For thos - e that - >> have SSI disabled, it'll act like a comment, so I wouldn't think it - would - >> break anything. + After you've done all that, you can add the following line to + index.shtml: + + + Note + + This line will be replaced with the actual HTML for the footer when + the page is requested, so you should put this line where you want the + footer to appear. + + Because this method depends on being able to use a #exec directive, + and most ISP's will not allow that, there is an alternative method. + You could have a small script (such as api.cgi) that basically looks + like: +#!/usr/bonsaitools/bin/perl -w + +require 'globals.pl'; + +if ($::FORM{sub} eq 'PutFooter') { + PutFooter(); +} else { + die 'api.cgi was incorrectly called'; +} + + and then put this line in index.shtml. + + + Note + + This still requires being able to use Server Side Includes, if this + simply will not work for you, see bug 80183 for a third option. A.4.8. Does Bugzilla provide any reporting features, metrics, graphs, etc? You know, the type of stuff that management likes to see. :) @@ -3765,46 +4596,40 @@ Appendix A. The Bugzilla FAQ find an excellent example at http://www.mozilla.org/quality/help/bugzilla-helper.html - A.4.14. Does Bugzilla allow fields to be added, changed or deleted? If - I want to customize the bug submission form to meet our needs, can I - do that using our terminology? - - Yes. - - A.4.15. Has anyone converted Bugzilla to another language to be used + A.4.14. Has anyone converted Bugzilla to another language to be used in other countries? Is it localizable? Currently, no. Internationalization support for Perl did not exist in a robust fashion until the recent release of version 5.6.0; Bugzilla is, and likely will remain (until 3.X) completely non-localized. - A.4.16. Can a user create and save reports? Can they do this in Word + A.4.15. Can a user create and save reports? Can they do this in Word format? Excel format? Yes. No. No. - A.4.17. Can a user re-run a report with a new project, same query? + A.4.16. Can a user re-run a report with a new project, same query? Yes. - A.4.18. Can a user modify an existing report and then save it into + A.4.17. Can a user modify an existing report and then save it into another name? You can save an unlimited number of queries in Bugzilla. You are free to modify them and rename them to your heart's desire. - A.4.19. Does Bugzilla have the ability to search by word, phrase, + A.4.18. Does Bugzilla have the ability to search by word, phrase, compound search? You have no idea. Bugzilla's query interface, particularly with the advanced Boolean operators, is incredibly versatile. - A.4.20. Can the admin person establish separate group and individual + A.4.19. Can the admin person establish separate group and individual user privileges? Yes. - A.4.21. Does Bugzilla provide record locking when there is + A.4.20. Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use or how are they notified? @@ -3812,19 +4637,19 @@ Appendix A. The Bugzilla FAQ detection, and offers the offending user a choice of options to deal with the conflict. - A.4.22. Are there any backup features provided? + A.4.21. Are there any backup features provided? MySQL, the database back-end for Bugzilla, allows hot-backup of data. You can find strategies for dealing with backup considerations at http://www.mysql.com/doc/B/a/Backup.html - A.4.23. Can users be on the system while a backup is in progress? + A.4.22. Can users be on the system while a backup is in progress? Yes. However, commits to the database must wait until the tables are unlocked. Bugzilla databases are typically very small, and backups routinely take less than a minute. - A.4.24. What type of human resources are needed to be on staff to + A.4.23. What type of human resources are needed to be on staff to install and maintain Bugzilla? Specifically, what type of skills does the person need to have? I need to find out if we were to go with Bugzilla, what types of individuals would we need to hire and how much @@ -3843,7 +4668,7 @@ Appendix A. The Bugzilla FAQ me three to five hours to make Bugzilla happy on a Development installation of Linux-Mandrake. - A.4.25. What time frame are we looking at if we decide to hire people + A.4.24. What time frame are we looking at if we decide to hire people to install and maintain the Bugzilla? Is this something that takes hours or weeks to install and a couple of hours per week to maintain and customize or is this a multi-week install process, plus a full @@ -3856,7 +4681,7 @@ Appendix A. The Bugzilla FAQ UNIX or Perl skills to handle your process management and bug-tracking maintenance & customization. - A.4.26. Is there any licensing fee or other fees for using Bugzilla? + A.4.25. Is there any licensing fee or other fees for using Bugzilla? Any out-of-pocket cost other than the bodies needed as identified above? @@ -3950,18 +4775,11 @@ Appendix A. The Bugzilla FAQ If you are using an alternate Mail Transport Agent (MTA other than sendmail), make sure the options given in the "processmail" script for - all instances of "sendmail" are correct for your MTA. If you are using - Sendmail, you may wish to delete the "-ODeliveryMode=deferred" option - in the "processmail" script for every invocation of "sendmail". (Be - sure and leave the "-t" option, though!) + all instances of "sendmail" are correct for your MTA. - A better alternative is to change the "-O" option to - "-ODeliveryMode=background". This prevents Sendmail from hanging your - Bugzilla Perl processes if the domain to which it must send mail is - unavailable. - - This is now a configurable parameter called "sendmailnow", available - from editparams.cgi. + If you are using Sendmail, try enabling "sendmailnow" in + editparams.cgi. If you are using Postfix, you will also need to enable + "sendmailnow". A.7.7. How come email never reaches me from bugzilla changes? @@ -4004,12 +4822,17 @@ Appendix A. The Bugzilla FAQ A.8.3. I think my database might be corrupted, or contain invalid entries. What do I do? - Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home - directory) to see! If it all comes back, you're OK. If it doesn't come - back OK (i.e. any red letters), there are certain things Bugzilla can - recover from and certain things it can't. If it can't auto-recover, I - hope you're familiar with mysqladmin commands or have installed - another way to manage your database... + Run the "sanity check" utility (./sanitycheck.cgi in the Bugzilla_home + directory) from your web browser to see! If it finishes without + errors, you're probably OK. If it doesn't come back OK (i.e. any red + letters), there are certain things Bugzilla can recover from and + certain things it can't. If it can't auto-recover, I hope you're + familiar with mysqladmin commands or have installed another way to + manage your database. Sanity Check, although it is a good basic check + on your database integrity, by no means is a substitute for competent + database administration and avoiding deletion of data. It is not + exhaustive, and was created to do a basic check for the most common + problems in Bugzilla databases. A.8.4. I want to manually edit some entries in my database. How? @@ -4065,10 +4888,10 @@ Appendix A. The Bugzilla FAQ A.8.9. How come even after I delete bugs, the long descriptions show up? - Delete everything from $BUZILLA_HOME/shadow. Bugzilla creates shadow - files there, with each filename corresponding to a bug number. Also be - sure to run syncshadowdb to make sure, if you are using a shadow - database, that the shadow database is current. + This should only happen with Bugzilla 2.14 if you are using the + "shadow database" feature, and your shadow database is out of sync. + Try running syncshadowdb -syncall to make sure your shadow database is + in synch with your primary database. 9. Bugzilla and Win32 @@ -4279,8 +5102,8 @@ Appendix A. The Bugzilla FAQ Try this link to view current bugs or requests for enhancement for Bugzilla. - You can view bugs marked for 2.14 release here. This list includes - bugs for the 2.14 release that have already been fixed and checked + You can view bugs marked for 2.16 release here. This list includes + bugs for the 2.16 release that have already been fixed and checked into CVS. Please consult the Bugzilla Project Page for details on how to check current sources out of CVS so you can have these bug fixes early! @@ -4300,8 +5123,7 @@ Appendix A. The Bugzilla FAQ A.11.3. What's the best way to submit patches? What guidelines should I follow? - 1. Enter a bug into bugzilla.mozilla.org for the "Webtools" product, - "Bugzilla" component. + 1. Enter a bug into bugzilla.mozilla.org for the "Bugzilla" product. 2. Upload your patch as a unified DIFF (having used "diff -u" against the current sources checked out of CVS), or new source file by clicking "Create a new attachment" link on the bug page you've @@ -4904,74 +5726,6 @@ C.3. MySQL Permissions & Grant Tables http://www.mysql.com/Manual/manual.html. _________________________________________________________________ -Chapter 7. Bugzilla Variants and Competitors - - I created this section to answer questions about Bugzilla competitors - and variants, then found a wonderful site which covers an awful lot of - what I wanted to discuss. Rather than quote it in its entirety, I'll - simply refer you here: http://linas.org/linux/pm.html - _________________________________________________________________ - -7.1. Red Hat Bugzilla - - Red Hat Bugzilla is probably the most popular Bugzilla variant on the - planet. One of the major benefits of Red Hat Bugzilla is the ability - to work with Oracle, MySQL, and PostGreSQL databases serving as the - back-end, instead of just MySQL. Dave Lawrence has worked very hard to - keep Red Hat Bugzilla up-to-date, and many people prefer the - snappier-looking page layout of Red Hat Bugzilla to the default - Mozilla-standard formatting. - - URL: http://bugzilla.redhat.com/bugzilla/ - _________________________________________________________________ - -7.2. Loki Bugzilla (Fenris) - - Fenris can be found at http://fenris.lokigames.com. It is a fork from - Bugzilla. - _________________________________________________________________ - -7.3. Issuezilla - - Issuezilla is another fork from Bugzilla, and seems nearly as popular - as the Red Hat Bugzilla fork. Some Issuezilla team members are regular - contributors to the Bugzilla mailing list/newsgroup. Issuezilla is not - the primary focus of bug-tracking at tigris.org, however. Their - Java-based bug-tracker, Scarab, a newfangled Java-based issue tracker, - is under heavy development and looks promising! - - URL: http://issuezilla.tigris.org/servlets/ProjectHome - _________________________________________________________________ - -7.4. Scarab - - Scarab is a promising new bug-tracking system built using Java Serlet - technology. As of this writing, no source code has been released as a - package, but you can obtain the code from CVS. - - URL: http://scarab.tigris.org - _________________________________________________________________ - -7.5. Perforce SCM - - Although Perforce isn't really a bug tracker, it can be used as such - through the "jobs" functionality. - - http://www.perforce.com/perforce/technotes/note052.htmlhttp://www.perf - orce.com/perforce/technotes/note052.html - _________________________________________________________________ - -7.6. SourceForge - - SourceForge is more of a way of coordinating geographically - distributed free software and open source projects over the Internet - than strictly a bug tracker, but if you're hunting for bug-tracking - for your open project, it may be just what the software engineer - ordered! - - URL: http://www.sourceforge.net - _________________________________________________________________ - Appendix D. Useful Patches and Utilities for Bugzilla Are you looking for a way to put your Bugzilla into overdrive? Catch @@ -5095,6 +5849,109 @@ D.4. The Quicksearch Utility has details. _________________________________________________________________ +D.5. Hacking Bugzilla + + What follows are some general guidelines for changing Bugzilla, and + adhering to good coding practice while doing so. We've had some + checkins in the past which ruined Bugzilla installations because of + disregard for these conventions. Sorry for the lack of formatting; I + got this info into the Guide on the day of 2.14 release and haven't + formatted it yet. + + The following is a guide for reviewers when checking code into Bugzill + a's + CVS repostory at mozilla.org. If you wish to submit patches to Bugzil + la, + you should follow the rules and style conventions below. Any code tha + t + does not adhere to these basic rules will not be added to Bugzilla's + codebase. + 1. Usage of variables in Regular Expressions + It is very important that you don't use a variable in a regular + expression unless that variable is supposed to contain an expressi + on. + This especially applies when using grep. You should use: + grep ($_ eq $value, @array); + - NOT - + grep (/$value/, @array); + If you need to use a non-expression variable inside of an expressi + on, be + sure to quote it properly (using \Q..\E). + Coding Style for Bugzilla + ------------------------- + While it's true that not all of the code currently in Bugzilla adheres + to + this styleguide, it is something that is being worked toward. Therefo + re, + we ask that all new code (submitted patches and new files) follow this + guide + as closely as possible (if you're only changing 1 or 2 lines, you don' + t have + to reformat the entire file :). + 1. Whitespace + Bugzilla's prefered indentation is 4 spaces (no tabs, please). + 2. Curly braces. + The opening brace of a block should be on the same line as the sta + tement + that is causing the block and the closing brace should be at the s + ame + indentation level as that statement, for example: + if ($var) { + print "The variable is true"; + } else { + print "Try again"; + } + - NOT - + if ($var) + { + print "The variable is true"; + } + else + { + print "Try again"; + } + 3. File Names + File names for bugzilla code and support documention should be leg + al across + multiple platforms. \ / : * ? " < > and | are all illegal charact + ers for + filenames on various platforms. Also, file names should not have + spaces in + them as they can cause confusion in CVS and other mozilla.org util + ities. + 4. Variable Names + If a variable is scoped globally ($::variable) its name should be + descriptive + of what it contains. Local variables can be named a bit looser, p + rovided the + context makes their content obvious. For example, $ret could be u + sed as a + staging variable for a routine's return value as the line |return + $ret;| will + make it blatently obvious what the variable holds and most likely + be shown + on the same screen as |my $ret = "";|. + 5. Cross Database Compatability + Bugzilla was originally written to work with MySQL and therefore t + ook advantage + of some of its features that aren't contained in other RDBMS softw + are. These + should be avoided in all new code. Examples of these features are + enums and + encrypt(). + 6. Cross Platform Compatability + While Bugzilla was written to be used on Unix based systems (and U + nix/Linux is + still the only officially supported platform) there are many who d + esire/need to + run Bugzilla on Microsoft Windows boxes. Whenever possible, we sh + ould strive + not to make the lives of these people any more complicated and avo + id doing things + that break Bugzilla's ability to run on multiple operating systems + . + _________________________________________________________________ + Appendix E. GNU Free Documentation License Version 1.1, March 2000 diff --git a/docs/xml/Bugzilla-Guide.xml b/docs/xml/Bugzilla-Guide.xml index 59befaf0a..8f2136bd8 100644 --- a/docs/xml/Bugzilla-Guide.xml +++ b/docs/xml/Bugzilla-Guide.xml @@ -26,7 +26,7 @@ -barnboy@NOSPAM.trilobyte.net"> +barnboy@trilobyte.net"> @@ -126,14 +126,14 @@ try to avoid clutter and feel free to waste space in the code to make it more re P. Barnson -
barnboy@NOSPAM.trilobyte.net
+
barnboy@trilobyte.net
Zach Lipton -
zach@NOSPAM.zachlipton.com
+
zach AT zachlipton DOT com
@@ -196,6 +196,9 @@ try to avoid clutter and feel free to waste space in the code to make it more re &future; + +&variants; + &faq; @@ -205,9 +208,6 @@ try to avoid clutter and feel free to waste space in the code to make it more re &database; - -&variants; - &patches; diff --git a/docs/xml/about.xml b/docs/xml/about.xml index 89f7bb127..04e054bc2 100644 --- a/docs/xml/about.xml +++ b/docs/xml/about.xml @@ -70,8 +70,7 @@ If you have any questions regarding this document, its copyright, or publishing this document in non-electronic form, - please contact &bzg-auth;. Remove "NOSPAM" from email address - to send. + please contact &bzg-auth;. @@ -172,8 +171,8 @@ Terry Weissman - for initially converting Bugzilla from BugSplat! and writing the - README upon which this documentation is largely based. + for initially writing Bugzilla and creating the + README upon which the UNIX installation documentation is largely based. Tara @@ -204,7 +203,8 @@ documentation (in no particular order): - Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron Teitelbaum + Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron + Teitelbaum, Jacob Steenhagen, Joe Robins
diff --git a/docs/xml/administration.xml b/docs/xml/administration.xml index 54f984fbc..98e726312 100644 --- a/docs/xml/administration.xml +++ b/docs/xml/administration.xml @@ -1192,6 +1192,103 @@ + + You may find this example illustrative for how bug groups work. + + Bugzilla Groups + +Bugzilla Groups example +----------------------- + +For this example, let us suppose we have four groups, call them +Group1, Group2, Group3, and Group4. + +We have 5 users, User1, User2, User3, User4, User5. + +We have 8 bugs, Bug1, ..., Bug8. + +Group membership is defined by this chart: +(X denotes that user is in that group.) +(I apologize for the nasty formatting of this table. Try viewing +it in a text-based browser or something for now. -MPB) + + G G G G + r r r r + o o o o + u u u u + p p p p + 1 2 3 4 + +-+-+-+-+ +User1|X| | | | + +-+-+-+-+ +User2| |X| | | + +-+-+-+-+ +User3|X| |X| | + +-+-+-+-+ +User4|X|X|X| | + +-+-+-+-+ +User5| | | | | + +-+-+-+-+ + +Bug restrictions are defined by this chart: +(X denotes that bug is restricted to that group.) + + G G G G + r r r r + o o o o + u u u u + p p p p + 1 2 3 4 + +-+-+-+-+ +Bug1| | | | | + +-+-+-+-+ +Bug2| |X| | | + +-+-+-+-+ +Bug3| | |X| | + +-+-+-+-+ +Bug4| | | |X| + +-+-+-+-+ +Bug5|X|X| | | + +-+-+-+-+ +Bug6|X| |X| | + +-+-+-+-+ +Bug7|X|X|X| | + +-+-+-+-+ +Bug8|X|X|X|X| + +-+-+-+-+ + +Who can see each bug? + +Bug1 has no group restrictions. Therefore, Bug1 can be seen by any +user, whatever their group membership. This is going to be the only +bug that User5 can see, because User5 isn't in any groups. + +Bug2 can be seen by anyone in Group2, that is User2 and User4. + +Bug3 can be seen by anyone in Group3, that is User3 and User4. + +Bug4 can be seen by anyone in Group4. Nobody is in Group4, so none of +these users can see Bug4. + +Bug5 can be seen by anyone who is in _both_ Group1 and Group2. This +is only User4. User1 cannot see it because he is not in Group2, and +User2 cannot see it because she is not in Group1. + +Bug6 can be seen by anyone who is in both Group1 and Group3. This +would include User3 and User4. Similar to Bug5, User1 cannot see Bug6 +because he is not in Group3. + +Bug7 can be seen by anyone who is in Group1, Group2, and Group3. This +is only User4. All of the others are missing at least one of those +group priveleges, and thus cannot see the bug. + +Bug8 can be seen by anyone who is in Group1, Group2, Group3, and +Group4. There is nobody in all four of these groups, so nobody can +see Bug8. It doesn't matter that User4 is in Group1, Group2, and +Group3, since he isn't in Group4. + + +
diff --git a/docs/xml/database.xml b/docs/xml/database.xml index aee9b37e5..7ff52134c 100644 --- a/docs/xml/database.xml +++ b/docs/xml/database.xml @@ -13,7 +13,7 @@ - + diff --git a/docs/xml/faq.xml b/docs/xml/faq.xml index 34b952b01..79fa528c4 100644 --- a/docs/xml/faq.xml +++ b/docs/xml/faq.xml @@ -620,6 +620,12 @@ progression states, also require adjusting the program logic to compensate for the change. + + There is no GUI for adding fields to Bugzilla at this + time. You can follow development of this feature at + http://bugzilla.mozilla.org/show_bug.cgi?id=91037 + @@ -633,42 +639,62 @@ - - This was a late-breaking question for the Guide, so I just have to - quote the relevant newsgroup thread on it. - - -> AFAIK, most sites (even if they have SSI enabled) won't have #exec cmd -> enabled. Perhaps what would be better is a #include virtual and a -> footer.cgi the basically has the "require 'CGI.pl' and PutFooter command. -> -> Please note that under most configurations, this also requires naming -> the file from index.html to index.shtml (and making sure that it will -> still be reconized as an index). Personally, I think this is better on -> a per-installation basis (perhaps add something to the FAQ that says how -> to do this). - -Good point. Yeah, easy enough to do, that it shouldn't be a big deal for -someone to take it on if they want it. FAQ is a good place for it. - -> Dave Miller wrote: -> ->> I did a little experimenting with getting the command menu and footer on ->> the end of the index page while leaving it as an HTML file... ->> ->> I was successful. :) ->> ->> I added this line: ->> ->> ->> ->> Just before the </BODY> </HTML> at the end of the file. And it worked. ->> ->> Thought I'd toss that out there. Should I check this in? For those that ->> have SSI disabled, it'll act like a comment, so I wouldn't think it would ->> break anything. - + + It's possible to get the footer on the static index page using + Server Side Includes (SSI). The trick to doing this is making + sure that your web server is set up to allow SSI and specifically, + the #exec directive. You should also rename index.html + to index.shtml. + + + After you've done all that, you can add the following line to + index.shtml: + + +]]> + + + + + This line will be replaced with the actual HTML for the footer + when the page is requested, so you should put this line where you + want the footer to appear. + + + + Because this method depends on being able to use a #exec directive, + and most ISP's will not allow that, there is an alternative method. + You could have a small script (such as api.cgi) + that basically looks like: + + + + and then put this line in index.shtml. + + +]]> + + + + + This still requires being able to use Server Side Includes, if + this simply will not work for you, see bug 80183 + for a third option. + + @@ -804,21 +830,6 @@ someone to take it on if they want it. FAQ is a good place for it. - - - - Does Bugzilla allow fields to be added, changed or deleted? If I want to - customize the bug submission form to meet our needs, can I do that using our - terminology? - - - - - Yes. - - - - @@ -1221,20 +1232,11 @@ someone to take it on if they want it. FAQ is a good place for it. If you are using an alternate Mail Transport Agent (MTA other than sendmail), make sure the options given in the "processmail" script for all - instances of "sendmail" are correct for your MTA. If you are using Sendmail, - you may wish to delete the "-ODeliveryMode=deferred" option in the - "processmail" script for every invocation of "sendmail". (Be sure and leave - the "-t" option, though!) - - - A better alternative is to change the "-O" option to - "-ODeliveryMode=background". This prevents Sendmail from hanging your - Bugzilla Perl processes if the domain to which it must send mail - is unavailable. + instances of "sendmail" are correct for your MTA. - This is now a configurable parameter called "sendmailnow", available - from editparams.cgi. + If you are using Sendmail, try enabling "sendmailnow" in editparams.cgi. + If you are using Postfix, you will also need to enable sendmailnow. @@ -1315,12 +1317,21 @@ someone to take it on if they want it. FAQ is a good place for it. - Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home - directory) to see! If it all comes back, you're OK. If it doesn't come back - OK (i.e. any red letters), there are certain things Bugzilla can recover - from and certain things it can't. If it can't auto-recover, I hope you're - familiar with mysqladmin commands or have installed another way to manage - your database... + Run the sanity check utility + (./sanitycheck.cgi in the + Bugzilla_home directory) from your web browser to see! If + it finishes without errors, you're + probably OK. If it doesn't come back + OK (i.e. any red letters), there are certain things + Bugzilla can recover from and certain things it can't. If + it can't auto-recover, I hope you're familiar with + mysqladmin commands or have installed another way to + manage your database. Sanity Check, although it is a good + basic check on your database integrity, by no means is a + substitute for competent database administration and + avoiding deletion of data. It is not exhaustive, and was + created to do a basic check for the most common problems + in Bugzilla databases. @@ -1428,10 +1439,12 @@ someone to take it on if they want it. FAQ is a good place for it. - Delete everything from $BUZILLA_HOME/shadow. Bugzilla creates shadow - files there, with each filename corresponding to a - bug number. Also be sure to run syncshadowdb to make sure, if you are using - a shadow database, that the shadow database is current. + This should only happen with Bugzilla &bz-ver; if you are + using the shadow database feature, and your + shadow database is out of sync. Try running + syncshadowdb + to make sure your shadow + database is in synch with your primary database. @@ -1752,14 +1765,14 @@ A: Sure! Here ya go! - Try + Try this link to view current bugs or requests for enhancement for Bugzilla. - You can view bugs marked for 2.14 release - here. - This list includes bugs for the 2.14 release that have already + You can view bugs marked for 2.16 release + here. + This list includes bugs for the 2.16 release that have already been fixed and checked into CVS. Please consult the Bugzilla Project Page for details on how to @@ -1800,8 +1813,9 @@ A: Sure! Here ya go! - Enter a bug into bugzilla.mozilla.org for the "Webtools" product, - "Bugzilla" component. + Enter a bug into bugzilla.mozilla.org for the Bugzilla + product. diff --git a/docs/xml/installation.xml b/docs/xml/installation.xml index 547d466ba..9cf100fdb 100644 --- a/docs/xml/installation.xml +++ b/docs/xml/installation.xml @@ -616,6 +616,15 @@ bash# mkdir /usr/bonsaitools/bin bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl + + Alternately, you can simply run this perl one-liner to + change your path to perl in all the files in your Bugzilla + installation: + +perl -pi -e 's@#!/usr/bonsaitools/bin/perl@/usr/bin/perl@' *cgi *pl Bug.pm + + Change the second path to perl to match your installation. + @@ -1241,7 +1250,7 @@ bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \ -
+
UNIX Installation Instructions History This document was originally adapted from the Bonsai @@ -1252,9 +1261,8 @@ bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \ The February 25, 1999 re-write of this page was done by Ry4an Brase <ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt, Martin Pool, & Dan Mosedale (But - don't send bug reports to them; report them using bugzilla, at - http://bugzilla.mozilla.org/enter_bug.cgi , project Webtools, - component Bugzilla). + don't send bug reports to them; report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla ). This document was heavily modified again Wednesday, March 07 @@ -1696,16 +1704,46 @@ exit; - Modify the invocation of all system() calls in all perl scripts in your Bugzilla directory. For instance, change this line in processmail: - -system ("./processmail.pl",@ARGLIST); - -to - + Modify the invocation of all system() calls in all perl + scripts in your Bugzilla directory. For instance, change + this line in processmail: + +system ("./processmail.pl",@ARGLIST); + to + system ("perl processmail.pl",@ARGLIST); + + + Add binmode() calls so attachments + will work (bug 62000). + + + Because Microsoft Windows based systems handle binary + files different than Unix based systems, you need to add + the following lines to + createattachment.cgi and + showattachment.cgi before the + require 'CGI.pl'; line. + + + + + + + + + According to bug 62000, the perl documentation says that you should always use binmode() when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting binmode() at the begining of the attachment files, there should be logic to determine if binmode() is needed or not. + + + @@ -1714,6 +1752,8 @@ system ("perl processmail.pl",@ARGLIST); relationships to Properties -> Home directory (tab) -> Application Settings (section) -> Configuration (button), such as: + + .cgi to: <perl install directory>\perl.exe %s %s .pl to: <perl install directory>\perl.exe %s %s @@ -1742,7 +1782,9 @@ GET,HEAD,POST registry at the following location: - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap + +HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap + The keys should be called ".pl" and ".cgi", and both @@ -1761,26 +1803,102 @@ GET,HEAD,POST If attempting to run Bugzilla 2.12 or older, you will need to remove encrypt() calls from the Perl source. This is not necessary for Bugzilla 2.13 and - later. + later, which includes the current release, Bugzilla + &bz-ver;. Removing encrypt() for Windows NT Bugzilla version 2.12 or earlier - Replace this: - -SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); -my $enteredcryptpwd = FetchOneColumn(); - - with this: - -my $enteredcryptpwd = $enteredpwd - + Replace this: + +SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); +my $enteredcryptpwd = FetchOneColumn(); + +with this: + +my $enteredcryptpwd = $enteredpwd + in cgi.pl.
+ +
+ Bugzilla LDAP Integration + + What follows is some late-breaking information on using the + LDAP authentication options with Bugzilla. The author has not + tested these (nor even formatted this section!) so please + contribute feedback to the newsgroup. + + +Mozilla::LDAP module + +The Mozilla::LDAP module allows you to use LDAP for authentication to +the Bugzilla system. This module is not required if you are not using +LDAP. + +Mozilla::LDAP (aka PerLDAP) is available for download from +http://www.mozilla.org/directory. + +NOTE: The Mozilla::LDAP module requires Netscape's Directory SDK. +Follow the link for "Directory SDK for C" on that same page to +download the SDK first. After you have installed this SDK, then +install the PerLDAP module. +---------------------------------------------------------------------- + +Post-Installation Checklist +---------------------------------------------------------------------- +Set useLDAP to "On" **only** if you will be using an LDAP directory +for authentication. Be very careful when setting up this parameter; +if you set LDAP authentication, but do not have a valid LDAP directory +set up, you will not be able to log back in to Bugzilla once you log +out. (If this happens, you can get back in by manually editing the +data/params file, and setting useLDAP back to 0.) + +If using LDAP, you must set the three additional parameters: + +Set LDAPserver to the name (and optionally port) of your LDAP server. +If no port is specified, it defaults to the default port of 389. (e.g +"ldap.mycompany.com" or "ldap.mycompany.com:1234") + +Set LDAPBaseDN to the base DN for searching for users in your LDAP +directory. (e.g. "ou=People,o=MyCompany") uids must be unique under +the DN specified here. + +Set LDAPmailattribute to the name of the attribute in your LDAP +directory which contains the primary email address. On most directory +servers available, this is "mail", but you may need to change this. +---------------------------------------------------------------------- + +(Not sure where this bit should go, but it's important that it be in +there somewhere...) +---------------------------------------------------------------------- +Using LDAP authentication for Bugzilla: + +The existing authentication scheme for Bugzilla uses email addresses +as the primary user ID, and a password to authenticate that user. All +places within Bugzilla where you need to deal with user ID (e.g +assigning a bug) use the email address. + +The LDAP authentication builds on top of this scheme, rather than +replacing it. The initial log in is done with a username and password +for the LDAP directory. This then fetches the email address from LDAP +and authenticates seamlessly in the standard Bugzilla authentication +scheme using this email address. If an account for this address +already exists in your Bugzilla system, it will log in to that +account. If no account for that email address exists, one is created +at the time of login. (In this case, Bugzilla will attempt to use the +"displayName" or "cn" attribute to determine the user's full name.) + +After authentication, all other user-related tasks are still handled +by email address, not LDAP username. You still assign bugs by email +address, query on users by email address, etc. +---------------------------------------------------------------------- + +

diff --git a/docs/xml/integration.xml b/docs/xml/integration.xml index e0547c365..36cc617e2 100644 --- a/docs/xml/integration.xml +++ b/docs/xml/integration.xml @@ -35,6 +35,14 @@ an @resolution field, you can even change the Bugzilla bug state. + + There is also a project, based upon somewhat dated Bugzilla + code, to integrate CVS and Bugzilla through CVS' ability to + email. Check it out at: + + http://homepages.kcbbs.gen.nz/~tonyg/, under the + cvszilla link. +
diff --git a/docs/xml/patches.xml b/docs/xml/patches.xml index 3a1ce90d2..3f49255f2 100644 --- a/docs/xml/patches.xml +++ b/docs/xml/patches.xml @@ -247,6 +247,104 @@ RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
+
+ Hacking Bugzilla + + What follows are some general guidelines for changing Bugzilla, and adhering to good coding practice while doing so. We've had some checkins in the past which ruined Bugzilla installations because of disregard for these conventions. Sorry for the lack of formatting; I got this info into the Guide on the day of 2.14 release and haven't formatted it yet. + + + +The following is a guide for reviewers when checking code into Bugzilla's +CVS repostory at mozilla.org. If you wish to submit patches to Bugzilla, +you should follow the rules and style conventions below. Any code that +does not adhere to these basic rules will not be added to Bugzilla's +codebase. + + 1. Usage of variables in Regular Expressions + + It is very important that you don't use a variable in a regular + expression unless that variable is supposed to contain an expression. + This especially applies when using grep. You should use: + + grep ($_ eq $value, @array); + + - NOT - + + grep (/$value/, @array); + + If you need to use a non-expression variable inside of an expression, be + sure to quote it properly (using \Q..\E). + +Coding Style for Bugzilla +------------------------- + +While it's true that not all of the code currently in Bugzilla adheres to +this styleguide, it is something that is being worked toward. Therefore, +we ask that all new code (submitted patches and new files) follow this guide +as closely as possible (if you're only changing 1 or 2 lines, you don't have +to reformat the entire file :). + + 1. Whitespace + + Bugzilla's prefered indentation is 4 spaces (no tabs, please). + + 2. Curly braces. + + The opening brace of a block should be on the same line as the statement + that is causing the block and the closing brace should be at the same + indentation level as that statement, for example: + + if ($var) { + print "The variable is true"; + } else { + print "Try again"; + } + + - NOT - + + if ($var) + { + print "The variable is true"; + } + else + { + print "Try again"; + } + + 3. File Names + + File names for bugzilla code and support documention should be legal across + multiple platforms. \ / : * ? " < > and | are all illegal characters for + filenames on various platforms. Also, file names should not have spaces in + them as they can cause confusion in CVS and other mozilla.org utilities. + + 4. Variable Names + + If a variable is scoped globally ($::variable) its name should be descriptive + of what it contains. Local variables can be named a bit looser, provided the + context makes their content obvious. For example, $ret could be used as a + staging variable for a routine's return value as the line |return $ret;| will + make it blatently obvious what the variable holds and most likely be shown + on the same screen as |my $ret = "";|. + + 5. Cross Database Compatability + + Bugzilla was originally written to work with MySQL and therefore took advantage + of some of its features that aren't contained in other RDBMS software. These + should be avoided in all new code. Examples of these features are enums and + encrypt(). + + 6. Cross Platform Compatability + + While Bugzilla was written to be used on Unix based systems (and Unix/Linux is + still the only officially supported platform) there are many who desire/need to + run Bugzilla on Microsoft Windows boxes. Whenever possible, we should strive + not to make the lives of these people any more complicated and avoid doing things + that break Bugzilla's ability to run on multiple operating systems. + + +
+ diff --git a/docs/xml/using.xml b/docs/xml/using.xml index 91a7658cd..934817081 100644 --- a/docs/xml/using.xml +++ b/docs/xml/using.xml @@ -399,13 +399,13 @@ system against which all others are measured. our Bugzilla database. Please notice the box is a scrollbox. Using the down arrow on the scrollbox, scroll down until you can see an entry - called "Webtools". Select this entry. + called "Bugzilla". Select this entry. Did you notice that some of the boxes to the right changed - when you selected "Webtools"? Every Program (or Product) + when you selected "Bugzilla"? Every Program (or Product) has different Versions, Components, and Target Milestones associated with it. A "Version" is the number of a software program. @@ -452,36 +452,67 @@ system against which all others are measured. Normally, a Component has a single Owner, who is responsible for overseeing efforts to improve that Component. - Mozilla Webtools Components + Mozilla's Bugzilla Components - Mozilla's "Webtools" Product is composed of several pieces (Components): + Mozilla's "Bugzilla" Product is composed of several pieces (Components): - Bonsai, - a tool to show recent changes to Mozilla - Bugzilla, - a defect-tracking tool - Build, - a tool to automatically compile source code - into machine-readable form - Despot, - a program that controls access to the other Webtools - LXR, - a utility that automatically marks up text files - to make them more readable - MozBot, - a "robot" that announces changes to Mozilla in Chat - TestManager, - a tool to help find bugs in Mozilla - Tinderbox, - which displays reports from Build + Administration, + Administration of a bugzilla installation, including + editcomponents.cgi, + editgroups.cgi, + editkeywords.cgi, + editparams.cgi, + editproducts.cgi, + editusers.cgi, + editversions.cgi, and + sanitycheck.cgi. + + Bugzilla-General, + Anything that doesn't fit in the other components, or spans + multiple components. + + Creating/Changing Bugs, + Creating, changing, and viewing bugs. + enter_bug.cgi, + post_bug.cgi, + show_bug.cgi and + process_bug.cgi. + + Documentation, + The bugzilla documentation, including anything in the + docs/ directory and The Bugzilla Guide + (This document :) + + Email, + Anything to do with email sent by Bugzilla. + processmail + + Installation, + The installation process of Bugzilla. This includes + checksetup.pl and whatever else it evolves into. + + Query/Buglist, + Anything to do with searching for bugs and viewing the buglists. + query.cgi and + buglist.cgi + + Reporting/Charting, + Getting reports from Bugzilla. + reports.cgi and + duplicates.cgi + + User Accounts, + Anything about managing a user account from the user's perspective. + userprefs.cgi, saved queries, creating accounts, + changing passwords, logging in, etc. + + User Interface, + General issues having to do with the user interface cosmetics (not + functionality) including cosmetic issues, HTML templates, etc. + - - A different person is responsible for each of these Components. - Tara Hernandez keeps - the "Bugzilla" component up-to-date. - -- cgit v1.2.3-24-g4f1b

Prev	Home	Next
The Quicksearch Utility	Up	GNU Free Documentation License