sharpsvn
Report a Bug

Report a Bug



To submit an Issue, you have to be an Observer in the SharpSvn project. Request to be an Observer.

Submiting an Issue

Before you file a new issue, please:

Please follow this process and keep the bug database clean so the AnkhSVN committers can focus on developing new code, rather than vetting the bug database.

What the Issue Fields Mean

When an issue is first filed, it automatically goes in the "---" target milestone, which indicates that the issue has not been processed yet. A developer will examine it and maybe talk to other developers, then estimate the bug's severity, the effort required to fix it, and schedule it in a numbered milestone, for example 1.1. (Or they may put it the unscheduled or nonblocking milestone, if they consider it tolerable for all currently planned releases.)

An issue filed under "unscheduled" might still get fixed soon, if a committer or patch contributor decides he or she wants it done. Putting it in unscheduled merely means it hasn't been scheduled for any particular release yet. The nonblocking milestone, on the other hand, means that we do not anticipate ever scheduling the issue for a particular release. This also does not mean the issue will never be fixed; it merely means that we don't plan to block any release on it.
Severity is represented in the Priority field. Here is how priority numbers map to severity:

  • P1: Prevents work from getting done, causes data loss, or BFI ("Bad First Impression").
  • P2: Workaround required to get stuff done.
  • P3: Like P2, but rarely encountered in normal usage.
  • P4: Developer concern only
  • P5: Nice to fix, but we can live with it.