Georg Brandl wrote: > Christian currently does a good job of assigning the correct properties > to new bugs. In any case, I'd prefer to keep a way to mark a bug as > "high-priority" (meaning that it should be fixed before the next release) > even if most of the bugs don't have an assigned priority. I've defined the priorities for me: low = nice to have feature normal = well ... pretty normal :) high = important, investigate the bug before the next release gets out urgent = bug breaks development or is a show stopper immediate = security issue or major development stopper Christian
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