>
>
>Ah, I see. Well, we're not there yet, but we will be eventually, so
>we should start planning for it.
>
>What keywords does Mozilla use? I presume `performance' is one of
>them, but there must be others. (I'm asking since we'll need a
>canonical list of keywords, if they're to be searchable. We don't
>have to copy all of Mozilla's right now, but it would be helpful to
>know what they've found useful.)
>
>
Well they use meta bugs and keywords both.
Generally meta bugs are used to track tasks that require a list of bugs
in order to consider the task complete. For instance, "[META] Checkout
Performance" and "[META] Commit Performance" might be some examples of
when meta bugs get used. These groupings are generally lists with a
possibly achievable goal. Some programmers also make these kinds of
bugs because that makes it easier to mass assign the group of bugs to
someone else later (by just changing the one meta bug).
Keywords generally describe a more generic idea such as
internationalization (intl), performance (perf), memory leaks (mlk),
etc, so that querying for bugs that affect this behavior show up
quickly. Mozilla also uses keywords for nominating bugs for milestones,
and the review team looks through all the mozilla1.0 (nominated) bugs
and sets them to either mozilla1.0- (reject) or mozilla1.0+ (accept) or
moves to next release (set to mozilla 1.1). They also have another
useful keyword called relnote, which indicates that with the next
release, there needs to be something in the Release Notes that describe
this bug.
***** Some examples of mozilla meta-bugs:
[META] outstanding issues for full HTML 4.01 support
[meta] Proxy bugs.
[META] O(N^2) algorithms in layout
[META] Mach-o MacOS X Build Blockers
***** Some examples of mozilla keywords:
meta A placeholder bug for tracking the progress of other bugs. Meta
bugs are made dependent on other bugs so that interested parties can be
kept up-to-date with status via one bug, without having to receive all
the mails related to all the bugs related to the development of a
particular area.
dataloss For bugs which that do not crash, but do cause critical data loss.
smoketest Means that this bug prevents the smoketests
<http://www.mozilla.org/quality/smoketests/> from passing.
mlk A memory leak bug - should be accompanied by a Purify (or
equivalent) log in order to mark as a confirmed mlk bug.
perf A performance issue: optimizations, coping with large files, page
loads, msg/folder load, etc.
footprint Bugs addressing footprint/code size issues.
arch Mozilla architecture issues - API cleanup, module restructuring and
redesign, platform coherency"
intl Use this keyword for any bug related to international issues.
relnote This bug need to be put on release notes for next milestone
announcement.
mozilla1.0.1 Add this keyword to propose that a bug must be fixed for
mozilla 1.0.1 To see whether a bug is likely to be fixed by this
milestone check the Target Milestone setting in the bug.
mozilla1.0.1+ drivers@mozilla.org will add this keyword to bugs that
have been evaluated as important to the Mozilla 1.0.1 release. This is
not an approval for checkin during freezes. To get approval to check
patches in please email drivers and look for the approval in the bug's
patch status.
mozilla1.0.1- drivers@mozilla.org will use this keyword to flag bugs
that are not critical to a Mozilla 1.0.1 release.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 29 20:22:40 2002