Cleanup ACE_HAS_PTHREAD_SIGMASK_PROTOTYPE, all platforms support it so far as I can...
[ACE_TAO.git] / ACE / docs / usage-bugzilla.html
blobe7f5876acfd62727dfee1ea6451fb4d572f06a2d
1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
2 <html>
3 <!-- -->
4 <head>
5 <title>DOC Center Bug Tracking System Usage</title>
6 </head>
8 <body text = "#000000" link="#000fff" vlink="#ff0f0f" bgcolor="#ffffff">
9 <h1>DOC Center Bug Tracking System Usage</h1>
11 <p>
12 The
13 <a href="https://www.dre.vanderbilt.edu">
14 Center for Distributed Object Computing</a> used the
15 Bugzilla
16 bug tracking system to keep track of existing problems and
17 enhancement requests. Currently <a href="https://github.com/DOCGroup/ACE_TAO/issues">
18 github issues</a> are used
20 <p>
21 To streamline our development process, you can now use it to
22 enter problem reports or make a request for a particular feature
23 that you'd like to see integrated into
24 <a href="https://www.dre.vanderbilt.edu/ACE">ACE</a>,
25 <a href="https://www.dre.vanderbilt.edu/TAO">TAO</a> or <a
26 href="https://www.dre.vanderbilt.edu/CIAO">CIAO</a>.
28 <p>
29 You can also use it to track the status of a particular bug or
30 enhancement. In addition, the bug tracking system can be used
31 to add comments and attachments that contain solutions or simple
32 test cases.
34 <p>
35 The bug tracking system is located at the following web site:
36 <samp>
37 <a href="http://bugzilla.dre.vanderbilt.edu/">
38 http://bugzilla.dre.vanderbilt.edu/
39 </a>
40 </samp>
42 <p>
43 If all you want to do is browse through the bugs in our bug
44 tracking system or view bug summary reports, then you can use
45 the bug tracking system right away.
47 <p>
48 Upon entering a bug or enhancement request for the first time,
49 you will be asked to enter an e-mail address. Once you've done
50 that, you will be mailed a password that you can use to log on
51 to the bug tracking system. You will only be asked to do this
52 once. Any changes to bug reports you submit will be mailed to
53 the e-mail address you provide.
55 <p>
56 Once you've logged on, you will have to ask for permissions through
57 the ACE mailing list to obtain permissions to enter bug
58 reports and modify existing ones. Other than adding comments,
59 fixes and attachments, please do not modify bug reports you
60 haven't submitted.
62 <p>
63 The bug tracking system is fairly straightforward to use. When
64 entering bug reports or enhancement requests, enter as much
65 information as possible. Most of the bug form fields provide
66 help if you are unsure what a particular field is used for.
68 <p>
69 For more information about using Bugzilla, and about bug
70 reporting in general, please see the following web sites:
72 <p>
73 <blockquote>
74 <samp>
75 <a href="http://www.mozilla.org/bugs">
76 http://www.mozilla.org/bugs/
77 </a><br>
78 <a href="http://www.mozilla.org/quality/bug-writing-guidelines.html">
79 http://www.mozilla.org/quality/bug-writing-guidelines.html
80 </a>
81 </samp>
82 </blockquote>
84 <p>
85 Keep in mind that the Bugzilla installation at the above web
86 site is <em>not</em> the same Bugzilla installation at the
87 Center for Distributed Object Computing. All bug reports and
88 enhancement requests for ACE and TAO should be done at the
89 Center for Distributed Object Computing's Bugzilla web site.
91 <hr>
92 <address><a href="mailto:ossama@dre.vanderbilt.edu">Ossama Othman</a></address>
93 <!-- Created: Wed Aug 18 14:45:31 EDT 1999 -->
94 <!-- hhmts start -->
95 Last modified:
96 <!-- hhmts end -->
97 <br>
98 Back to <a href="index.html">ACE Documentation Home</a>.
99 </body>
100 </html>