- The Book of Dojo
- The Dojo Book, 0.4
- Part 1: "Introduction"
- Part 2: "Out of the Box" Dojo
- Part 3: "The Dojo Programming Model"
- Part 4: "More on Widgets"
- Part 5: "Connecting the pieces"
- Part 6: "Customizing Dojo Builds for Better Performance"
- Part 7: "Utilities"
- Part 8: "Internationalization and Accessiblity"
- Part 9: "Dojo Community"
- Part 10: "Fresh From The Shed" Dojo
- BookWriting
- Glossary
Filing Bugs And Patches
Submitted by alex on Mon, 01/01/2007 - 19:28.
The Dojo bug database is located at http://trac.dojotoolkit.org. You need to login with your dojotoolkit.org user name and password before filing bugs. If you don't already have an account, you can sign up for one here.
You don't need to sign a Contributor License Agreementto submit bugs, although you do need to sign it before submitting patches. See this post for a fuller explanation of why we insist on CLAs for patches.
A good bug report should include:
- Version of Dojo and build name if applicable
- Browser versions and platforms where the bug occurs
- Error messages displayed (if any)
- A contact address so we can follow-up with you
- Describe the exact situation in which the bug occurs as precisely as possible. Is it reproducible? Did it break in a certain release? Is it still an issue with nightly or subversion head? etc.
- Testcases and patchces are even better.
- Version is the version of Dojo in which you have the issue (usually the current release), and milestone is the version in which it will be fixed. Unless you are a Dojo commiter, we prefer that you leave milestone blank so we can triage it as appropriate.
