File:  [LON-CAPA] / loncom / html / adm / help / tex / Bugzilla.tex
Revision 1.1: download - view: text, annotated - select for diffs
Wed Sep 3 20:42:32 2003 UTC (20 years, 10 months ago) by bowersj2
Branches: MAIN
CVS tags: version_1_1_X, version_1_1_3, version_1_1_2, version_1_1_1, version_1_1_0, version_1_0_99_3, version_1_0_99_2, version_1_0_99_1, version_1_0_99, HEAD
Add these files.

    1: \label{Bugzilla}
    2: LON-CAPA uses "Bugzilla" (http://www.bugzilla.org/) to report and track bugs 
    3: and enhancements.  To use Bugzilla, you will need to have an account with 
    4: Bugzilla. You can create an account at http://bugs.lon-capa.org and then 
    5: select \textbf{Open a New Account}. To report a bug or request an enhancement, do 
    6: the following:
    7: 
    8: \begin{enumerate}
    9: 
   10:  Open the web page http://bugs.lon-capa.org
   11: 2. Select enter a new bug report.
   12: 3. Select the product (LON-CAPA) on which to enter a bug.
   13: 4. At the login screen, enter your email address and password.
   14: 5. Click Login.
   15: 6. Select the version of LON-CAPA, the LON-CAPA component the bug is in, the platform 
   16: your using, and the operating system your using from the pull down menu.
   17: 7. Enter a summary in the summary text box.
   18: 8. Enter a description in the description text box.
   19: 9. Click Commit.
   20: 
   21: \end{enumerate}
   22: 
   23: LON-CAPA is open-source software where everyone is free to contribute to the 
   24: development. If you think of an enhancement request, or find a bug in the system, 
   25: please report it. All reported bugs and enhancement requests posted on Bugzilla
   26: will be examined by the core LON-CAPA team. Having the request in Bugzilla
   27: makes it much easier to keep track of bugs and enhancement requests, making it
   28: less likely such things will get lost or be forgetten as requests not in 
   29: Bugzilla frequently are.
   30: 
   31: Bugzilla also supports conversation about requests, and some workflow and 
   32: accountability features. You'll be able to see how the developers respond to
   33: the bug, who is currently responsible for it, and what the developer's intention
   34: is.
   35: 

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>