>
>
>"Performance" is nebulous enough that if we have a meta-issue for it,
>we'll never feel we can close it.
>
>
Meta issues should almost never be closed.
>Nor will the keyword really help. If people do remember to use it,
>then they'll assign it to any issue that is performance-related, even
>if the issue is minor enough that it's not a concern for you. If they
>don't remember to use it, then it's not helping you. And finally, if
>it's just you marking up the issues that concern you, then the keyword
>should be named "behle-performance" :-) ... But for obvious reasons,
>it's not sustainable to start tracking individual users' needs across
>the issue tracker.
>
>
I had planned on tracking all performance issues whether they are import
or minor, and it's not necessarily the list of bugs that I need fixed,
but rather all the bugs that affect performance.
>Is it difficult for you to just watch the issue db and manually track
>the issues that matter to you?
>
>
I'm just use to working on Mozilla where you have thousands of bugs that
are performance related and there is no possible way to track them all
short of meta tracking bugs or keywords. The more difficult part is
finding these bugs in all the soup as there is no way to quickly query
for bugs that are performance related. (Unless of course every person
who entered a bug said, "This bug makes performance really bad!")
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 29 17:36:31 2002