Last modified: 2012-05-08 13:55:04 UTC
Being able to search for particular keywords or phrases in commit summaries or diffs can greatly help in tracking down a change. It may be feasible to stuff custom entries into the searchindex table (w/ MySQL search) or indirectly into the search engine (w/ Lucene), but this may require infrastructure for a clean search engine update interface. Being able to restrict the search by branch or path, date, or committer would be suitably useful with this. Identifying classes/methods/functions altered even when their definition lines don't appear in the diff would be *very* helpful, but might be harder. (Break these out to separate bugs if not initially built with the other stuff.)
Krinkle's got a grep thingy on toolserver which can help until something's more tightly integrated: http://toolserver.org/~krinkle/wikimedia-svn-search/view.php?id=73&hash=2b7dc3d581c46613e69c42cc003cbf3a#F2L2788
Mark, are we going back to using priorities for something? We usually just tend to ignore them...
Reedy, feel free to ignore them. I'm marking them for me, mostly. If I want you guys to start paying attention, I'll let you know.
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
