Guidelines for MTOS Case Submission

Before Reporting a Bug

• Please search FogBugz to see if your bug has already been submitted.
• If you find a match, please don’t submit a duplicate case. Instead, annotate the existing case with any info from your own experience might be helpful.
  • If you can’t think of anything new to add, just saying “+1” or “I saw this too” will help us know the total number of users the bug is affecting.

Filing Your Bug

• Click new case and begin entering your bug report.
• Title the case with something accurate and distinctive (ie, titling it “MTOS bug” will make it decrease the chance of us responding to the bug in a timely fashion.)
• In the large text field beneath “Opened by” please tell us:
  • Steps you took that caused the bug.
  • What you expected to happen.
  • What actually happened.
  • Salient information about your MTOS set up including:
    • Server OS/platform (Linux, Windows XP, Mac OS X. etc.)
    • Database and version
    • Other related software on your server you may be using such as FastCGI or mod_perl
• Enter the version # of the MTOS install where the bug occurred in the Version field.
• Set the Project to “Movable Type Open Source”. You don’t need to edit any of the other fields.

• If you have a code patch you would like to submit, please include it with the bug report, either as an attached file or if it is a short enough diff, pasted into the case itself.

• To submit code patches to Six Apart you must read and agree to the MTOS Contributor Agreement. You will be sent that the first time you submit a bug report with a code patch. Six Apart can not accept any code patches from non-employees without an agreement on record.

• In order for the case to be properly triaged, it must show up in our bug triage filter. That means that it must be assigned to “Bug Triage User” and the fix-for must “Undecided.”
• Do not change the Fix-For of the case — doing so can result in your bug report being lost or deleted.
• Do not change the Assigned To of the case — doing so can result in your bug report being lost or deleted.
• Repeated violation of these guidelines can result in your MTOS FogBugz account being suspended or deleted.

After the Bug Has Been Submitted

• Once your bug is submitted, it will be placed in bug triage for evaluation by the Movable Type product team.
• A Six Apart QA engineer may contact you for further details about your bug if they are not able to reproduce it.
• You can check the status of your bug by logging into FogBugz and searching for the case #.
• If you wish to add more info to the case, please feel free to do so. Please do not change any of the other fields of the bug once it has been submitted, as that can cause the bug to become lost.
• If you later realize your bug report was actually user error, please let us know, but don’t close it! Even if it wasn’t actually a bug, it can still be helpful for us to review such cases as it helps us know what areas of the product are confusing—even if it wasn’t a software fault, per se, it might still indicate a usability problem that we need to attend to.