|
Last change
on this file since 28897 was 28897, checked in by davidb, 10 years ago |
|
GUI front-end to server base plus web page content
|
|
File size:
1.2 KB
|
| Line | |
|---|
| 1 | # The issues section is for bug reports and feature requests only. If you need help, please use [stackoverflow](http://stackoverflow.com/questions/tagged/three.js).
|
|---|
| 2 |
|
|---|
| 3 |
|
|---|
| 4 | Before reporting a bug
|
|---|
| 5 | ---
|
|---|
| 6 | 1. Search issue tracker for similar issues.
|
|---|
| 7 | 2. Try the latest dev branch version of three.js.
|
|---|
| 8 | 3. Refer to the [Migration Guide](https://github.com/mrdoob/three.js/wiki/Migration) when upgrading to the dev version.
|
|---|
| 9 |
|
|---|
| 10 |
|
|---|
| 11 | How to report a bug
|
|---|
| 12 | ---
|
|---|
| 13 | 1. Specify the revision number of the three.js library where the bug occurred.
|
|---|
| 14 | 2. Specify your browser version, operating system, and graphics card. (for example, Chrome 23.0.1271.95, Windows 7, Nvidia Quadro 2000M)
|
|---|
| 15 | 3. Describe the problem in detail. Explain what happened, and what you expected would happen.
|
|---|
| 16 | 4. Provide a small test-case (http://jsfiddle.net). If a test-case is not possible, provide a link to a live version of your application.
|
|---|
| 17 | 5. If helpful, include a screenshot. Annotate the screenshot for clarity.
|
|---|
| 18 |
|
|---|
| 19 |
|
|---|
| 20 | How to contribute to three.js
|
|---|
| 21 | ---
|
|---|
| 22 | 1. Make sure you have a GitHub account.
|
|---|
| 23 | 2. Fork the repository on GitHub.
|
|---|
| 24 | 3. Check the [Contribution Guidelines](https://github.com/mrdoob/three.js/wiki/How-to-contribute-to-three.js).
|
|---|
| 25 | 4. Make changes to your clone of the repository.
|
|---|
| 26 | 5. Submit a pull request.
|
|---|
| 27 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
