File:
[LON-CAPA] /
loncom /
html /
adm /
help /
tex /
Bugzilla.tex
Revision
1.3:
download - view:
text,
annotated -
select for diffs
Tue Jun 8 21:54:57 2004 UTC (20 years, 2 months ago) by
felicia
Branches:
MAIN
CVS tags:
version_1_3_X,
version_1_3_3,
version_1_3_2,
version_1_3_1,
version_1_3_0,
version_1_2_X,
version_1_2_99_1,
version_1_2_99_0,
version_1_2_1,
version_1_2_0,
version_1_1_99_5,
version_1_1_99_4,
version_1_1_99_3,
version_1_1_99_2,
version_1_1_99_1,
HEAD
----------------------------------------------------------------------
Put \item in between enumerate so enumerate actually works
Modified Files:
Bugzilla.tex
----------------------------------------------------------------------
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: \item Open the web page http://bugs.lon-capa.org
11: \item Select enter a new bug report.
12: \item Select the product (LON-CAPA) on which to enter a bug.
13: \item At the login screen, enter your email address and password.
14: \item Click Login.
15: \item Select the version of LON-CAPA, the LON-CAPA component the bug is in, the platform your using, and the operating system your using from the pull down menu.
16: \item Enter a summary in the summary text box.
17: \item Enter a description in the description text box.
18: \item Click Commit.
19:
20: \end{enumerate}
21:
22: LON-CAPA is open-source software where everyone is free to contribute to the
23: development. If you think of an enhancement request, or find a bug in the system,
24: please report it. All reported bugs and enhancement requests posted on Bugzilla
25: will be examined by the core LON-CAPA team. Having the request in Bugzilla
26: makes it much easier to keep track of bugs and enhancement requests, making it
27: less likely such things will get lost or be forgotten as requests not in
28: Bugzilla frequently are.
29:
30: Bugzilla also supports conversation about requests, and some workflow and
31: accountability features. You'll be able to see how the developers respond to
32: the bug, who is currently responsible for it, and what the developer's intention
33: is.
34:
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>