> > But how should a performance improvement be filed? Bug? Feature request? > > Or should "feature request" be renamed "improvement"? > > It's a feature request (since we won't backport it unless there is a > genuine performance problem being addressed as a bug fix). Whether > that warrants changing the name, I don't know. I think most people won't intuitively file performance issues as "feature requests", since it doesn't sound like a feature. > A third option for > "other improvement" may also work (since that would also cover things > like clarifying doc wording, fixing comments, adjusting code to be > more readable/obviously correct, etc). But then why not keep a clear categorization of these "other improvements"? By the way, doc wording fixes and cosmetic code changes often get backported. :) cheers Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4