[BACK]Return to Bugzilla.tex CVS log [TXT] [DIR] Up to [LON-CAPA] / loncom / html / adm / help / tex
File:  [LON-CAPA] / loncom / html / adm / help / tex / Bugzilla.tex
Revision 1.7: download - view: text, annotated - select for diffs
Sun Jun 19 17:58:59 2005 UTC (19 years, 1 month ago) by felicia
Branches: MAIN
CVS tags: version_2_1_X, version_2_1_99_0, version_2_1_3, version_2_1_2, version_2_1_1, version_2_1_0, version_2_0_X, version_2_0_99_1, version_2_0_2, version_2_0_1, version_2_0_0, version_1_99_3, version_1_99_2, version_1_99_1, version_1_99_0, HEAD
Edited a bunch of help files and added many new ones so the cc manual no contains everything that my Training Guide contains. Next step is to edit the files for readability and consistancy in format.

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