Difference between revisions of "Bug Reporting"

From Jmol
Jump to navigation Jump to search
m (Playing with templates)
m
Line 5: Line 5:
 
* There's also the Jmol developers list {{mail|jmol-developers@lists.sf.net}}, but less people are receiving mails from this list and developers are also receiving mails from the users list, so use this list only if you're absolutely sure it's a bug.
 
* There's also the Jmol developers list {{mail|jmol-developers@lists.sf.net}}, but less people are receiving mails from this list and developers are also receiving mails from the users list, so use this list only if you're absolutely sure it's a bug.
  
Once the bug has been confirmed, you can open a [https://sourceforge.net/tracker/?group_id=23629&atid=379133 Bug Report].
+
Once the bug has been confirmed, you can open a [https://sourceforge.net/tracker/?group_id=23629
 
 
If you want to submit a patch, you can open a [https://sourceforge.net/tracker/?group_id=23629&atid=379135 Patch Request].
 
 
 
If you think of a new feature to add to Jmol, you can discuss it in the mailing lists or open a [https://sourceforge.net/tracker/?group_id=23629&atid=379136 Feature Request].
 

Revision as of 19:39, 10 April 2007

How to report a bug in Jmol ?

If you find something that looks like a bug in Jmol, you should post a mail in one of the Jmol Mailing Lists :

  • Preferably in the Jmol users list jmol-users@lists.sf.net, where you can get help for several people to decide if it's really a bug and maybe find a way to go around it.
  • There's also the Jmol developers list jmol-developers@lists.sf.net, but less people are receiving mails from this list and developers are also receiving mails from the users list, so use this list only if you're absolutely sure it's a bug.

Once the bug has been confirmed, you can open a [https://sourceforge.net/tracker/?group_id=23629