Thanks for the examples!
Okay, sounds like a `performance' keyword would indeed be useful here
(and more useful than a meta issue, given your goals and the way we
usually schedule issues). Since it's still up to you to decide what
issues you care about, it's okay that this keyword may be attached to
more issues than actually block your adoption of Subversion.
Would you like to go ahead and add it to the relevant issues?
I imagine we'll sometimes forget to add the keyword to new issues that
should have it, but that's what Old Hundred Eyes is for...
-Karl
Brandon Ehle <azverkan@yahoo.com> writes:
> ***** 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 22:10:55 2002