##How to raise issues
1. Create a bug report.
-2. Add in any links from the mailing list or IRC logs to the bug report for back tracking
- (this is mandatory). Also fill in the URL field if there is a relevant wiki page.
+2. Add in any links from the mailing list or IRC logs to the bug report for
+back tracking (this is mandatory). Also fill in the URL field if there is a
+relevant wiki page.
3. CC in relevant team members
-4. make absolutely sure to fill in "blocks", "depends on" or "see also" so that the
- bug is not isolated (otherwise bugs are too hard to find if isolated from everything else)
+4. Make absolutely sure to fill in "blocks", "depends on" or "see also" so
+that the bug is not isolated (otherwise bugs are too hard to find if isolated
+from everything else)
5. Ping on IRC to say a bug has been created
6. Unless you know exactly which milestone to use, leave blank initially. This
also applies when editing milestone, budget parent/child, toml fields. See