summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorschmidt <douglascraigschmidt@users.noreply.github.com>2006-04-09 20:18:46 +0000
committerschmidt <douglascraigschmidt@users.noreply.github.com>2006-04-09 20:18:46 +0000
commit036a64d4d47d44f6dd4d0c8e7711feaedccbfa0d (patch)
tree3b79786423b3298d9a721a76a978f43fabd1593d
parent252dacc33f0cf5e4706440723fe2154194b32baf (diff)
downloadATCD-036a64d4d47d44f6dd4d0c8e7711feaedccbfa0d.tar.gz
ChangeLogTag:Sun Apr 9 12:00:00 2006 Douglas C. Schmidt <schmidt@cse.wustl.edu>
-rw-r--r--ChangeLog7
-rw-r--r--THANKS1
-rw-r--r--docs/ACE-bug-process.html163
-rw-r--r--docs/index.html11
4 files changed, 103 insertions, 79 deletions
diff --git a/ChangeLog b/ChangeLog
index 7d0c56f21dd..5092c9c17e4 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+Sun Apr 9 12:00:00 2006 Douglas C. Schmidt <schmidt@cse.wustl.edu>
+
+ * docs/ACE-bug-process.html: Updated this page to more accurately
+ reflect how the DOC group handles enhancement requests. Thanks
+ to David White <david dot white dot 7 at gmail dot com> for
+ motivating this.
+
Sat Apr 8 18:32:29 2006 Douglas C. Schmidt <schmidt@cse.wustl.edu>
* ace/Shared_Memory_MM.h (ACE_Shared_Memory_MM):
diff --git a/THANKS b/THANKS
index 1557c415952..afdb05fc29a 100644
--- a/THANKS
+++ b/THANKS
@@ -2097,6 +2097,7 @@ Aleksandar Vukajlovic <vukajlo at finsoft dot co dot yu>
Ignacio Alvarez <support at xentient dot com>
Sergey Zubarev <sergant128 at mail dot ru>
Qingbo Cai <qingbo dot cai at case dot edu>
+David White <david dot white dot 7 at gmail dot com>
I would particularly like to thank Paul Stephenson, who worked with me
at Ericsson in the early 1990's. Paul devised the recursive Makefile
diff --git a/docs/ACE-bug-process.html b/docs/ACE-bug-process.html
index 557bdb7eb5c..ec3699165ec 100644
--- a/docs/ACE-bug-process.html
+++ b/docs/ACE-bug-process.html
@@ -1,44 +1,50 @@
<!-- $Id$ -->
<HTML>
- <TITLE>ACE+TAO Bug Fixing Policies</TITLE>
+ <TITLE>ACE, TAO, and CIAO Bug Fixing Policies</TITLE>
<BODY text = "#000000" link="#000fff" vlink="#ff0f0f" bgcolor="#ffffff">
<HR>
-<H3>ACE+TAO Bug Fixing Policies</H3>
+<H3>ACE, TAO, and CIAO Bug Fixing Policies</H3>
-As <A HREF="http://www.dre.vanderbilt.edu/ACE">ACE</A>,and <A
-HREF="http://www.dre.vanderbilt.edu/TAO">TAO</A> have grown in
-popularity the volume of mail on the
-<A HREF="http://www.cs.wustl.edu/~schmidt/ACE-mail.html">ACE+TAO users
-mailing list</A> and USENET newsgroup <A
+As <A HREF="http://www.dre.vanderbilt.edu/ACE/">ACE</A>, <A
+HREF="http://www.dre.vanderbilt.edu/TAO/">TAO</A>, and <A
+HREF="http://www.dre.vanderbilt.edu/CIAO/">CIAO</A> have grown in
+popularity the volume of mail on the <A
+HREF="http://www.cs.wustl.edu/~schmidt/ACE-mail.html">mailing
+lists</A> and USENET newsgroup <A
HREF="news:comp.soft-sys.ace">comp.soft-sys.ace</A> has grown
considerably. While this increase is healthy, and a natural
-consequence of the larger number of ACE and TAO users, it is straining
-the resources of the DOC <A
-HREF="http://www.cs.wustl.edu/~schmidt/ACE-members.html">research
+consequence of the larger number of ACE, TAO, and CIAO users, it is
+straining the resources of the researchers in the <A
+HREF="http://www.cs.wustl.edu/~schmidt/ACE-members-i.html">DOC
group</A> at <A
HREF="http://www.cs.wustl.edu/~schmidt/doc-center.html">Washington
University</A>, <A HREF="http://zen.uci.edu">UC Irvine</A> and <A
-HREF="http://www.dre.vanderbilt.edu"> ISIS</A> to
-respond to all the traffic immediately. Moreover, our prompt bug
-fixes may actually be discouraging the creation of a larger community
-of users who have deep knowledge of how ACE and TAO work and can help
-provide bug fixes and new features. <P>
-
-For us to continue supporting ACE and TAO effectively and to allow the
-ACE and TAO user community to evolve, please make it a point to abide
-by the following policies:
+HREF="http://www.dre.vanderbilt.edu">ISIS</A> to respond to all the
+traffic immediately. Prompt bug fixes from the DOC group also
+discourage the creation of a larger community of <A
+HREF="http://www.cs.wustl.edu/~schmidt/ACE-members.html">users</A> and
+<A
+HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.htlm">commercial
+support companies</A> who have deep knowledge of how ACE, TAO, and
+CIAO work and can help provide bug fixes and new features. <P>
+
+To ensure the continued growth and maturation of ACE, TAO, and CIAO,
+and to allow the user and vendor communities to evolve, please make it
+a point to abide by the following policies:
<UL>
-<LI> All bug reports to the ACE+TAO <A
+<LI> All bug reports to the <A
HREF="http://www.cs.wustl.edu/~schmidt/ACE-mail.html">mailing
lists</A> should be submitted using the appropriate bug report form in
<A HREF="../PROBLEM-REPORT-FORM">$ACE_ROOT/PROBLEM-REPORT-FORM</A>
-(for ACE) or <A
+(for ACE), <A
HREF="../TAO/PROBLEM-REPORT-FORM">$TAO_ROOT/PROBLEM-REPORT-FORM</A>
-(for TAO). Please use these forms since bug reports that are not
+(for TAO), <A
+HREF="../TAO/CIAO/PROBLEM-REPORT-FORM">$CIAO_ROOT/PROBLEM-REPORT-FORM</A>
+(for CIAO). Please use these forms since bug reports that are not
submitted in this form are likely to fall through the cracks. Here is
our policy for addressing these bug reports: <P>
@@ -50,43 +56,40 @@ our work we will respond to it in a very timely manner. Please
contact <A HREF="mailto:schmidt@cs.wustl.edu">me</A> if you'd like to
become a sponsor. <P>
-<LI> If it's a bug report along with a fix we will also apply this
-in a timely manner. In general, people who submit good bug
- reports with fixes tend to get much better help from the core DOC
- group team, irrespective of whether they are sponsors or not since
- they are helping our overall effort move ahead. <P>
+<LI> If it's a bug report along with a fix we will try to apply this
+in a timely manner. In general, people who submit good bug reports
+with fixes tend to get much better help from the core DOC group team,
+irrespective of whether they are sponsors or not since they are
+helping our overall effort move ahead. <P>
-<LI> If it's a bug report that will prevent ACE or TAO from working on
-a major platform used by our sponsors we'll try to fix it as time
-permits. <P>
+<LI> If it's a bug report that prevents ACE, TAO, or CIAO from working
+on a major platform used by ourselves or our sponsors we'll try to fix
+it as time permits. <P>
</OL>
<LI> You should also consider entering your bug report into our <A
HREF="http://deuce.doc.wustl.edu/bugzilla/index.cgi">bug tracking
-database</A> so that it's archived for future processing. We try to
-address these bugs as time permits, but may not get to them for a
-while unless it affects our work or the work of our sponsors. If
-you'd like an immediate response, please contact <A
-HREF="mailto:schmidt@cs.wustl.edu">me</A> about becoming a sponsor or
-contact one of the companies that provides <A
-HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">
-commercial support</A> for ACE+TAO. <P>
+database</A> so that it's archived for future processing. As usual,
+we try to address these bugs as time permits, but may not get to them
+for a while unless it affects our work or the work of our
+sponsors. <P>
We encourage bug reports for those without support to be posted
initially to the <A
HREF="http://www.cs.wustl.edu/~schmidt/ACE-mail.html">ACE users</A>
-(<A HREF="mailto:ace-users@cs.wustl.edu">ace-users@cs.wustl.edu</A>)
-or <A HREF="http://www.cs.wustl.edu/~schmidt/TAO-mail.html">TAO
+(<A HREF="mailto:ace-users@cs.wustl.edu">ace-users@cs.wustl.edu</A>),
+<A HREF="http://www.cs.wustl.edu/~schmidt/TAO-mail.html">TAO users</A>
+(<A HREF="mailto:tao-users@cs.wustl.edu">tao-users@cs.wustl.edu</A>),
+and <A HREF="http://www.cs.wustl.edu/~schmidt/CIAO-mail.html">CIAO
users</A> (<A
-HREF="mailto:tao-users@cs.wustl.edu">tao-users@cs.wustl.edu</A>)
-mailing lists, where the ACE+TAO user community may already have
-developed, or have an interest in developing, a solution. While the
-core ACE+TAO development team participates in this mailing list, we
-can not guarantee responses to all postings. <P>
+HREF="mailto:ciao-users@cs.wustl.edu">ciao-users@cs.wustl.edu</A>)
+mailing lists, where the open-source user community may already have
+developed, or have an interest in developing, a solution. <P>
-<LI> If you post something and don't get a reply, please do
- the following:<P>
+<LI> While the core DOC group development team participates in this
+mailing list, we cannot response to all postings. Therefore, if you
+post something and don't get a reply, please do the following:<P>
<UL>
<LI>
@@ -95,43 +98,47 @@ can not guarantee responses to all postings. <P>
HREF="http://groups.google.com/groups?q=comp.soft-sys.ace&ie=UTF-8&oe=UTF-8&hl=en">comp.soft-sys.ace</A> newsgroup to see if your posting is visible. <P>
<LI> If it's not visible, please make sure you're
- <A HREF="http://www.cs.wustl.edu/~schmidt/ACE-mail.html">subscribed to the mailing
+ <A HREF="http://www.cs.wustl.edu/~schmidt/ACE-mail.html">subscribed
+to the mailing
list(s)</A> you sent the report to since we have a "members only" posting
requirement to minimize spam. <P>
<LI> If it is visible and you haven't received a reply this probably means
that either no one knows the answer or no one has time to answer it.
As always, if you need more predictable help please contact one of
- <A HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">commercial support</a> companies for ACE+TAO.<P>
+ <A
+HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">commercial
+support</a> companies for ACE+TAO.<P>
</UL>
<LI> If you find a problem with a version of TAO that was released by
<A HREF="http://www.theaceorb.com/">OCI</A> then please report it
to <A
- HREF="mailto:taosupport@ociweb.com">taosupport@ociweb.com</A> since
- their version of TAO is somewhat different from the DOC group's
+ HREF="mailto:taosupport@ociweb.com">taosupport@ociweb.com</A>
+ since their version of TAO is different from the DOC group's
version of TAO and thus they provide their own support. <P>
-<LI> If it's a general question about how to use ACE or TAO feature
-we'll try to respond as time permits, though we will also rely on the
-experience of the ACE and TAO user community to field these types of
-questions, as well. If you have a question about TAO, you should
-first check out the TAO <A HREf="http://www.theaceorb.com/faq/">online
-FAQ</A> to see if your question has already been answered. If you
-require consulting support for ACE and/or TAO, please contact one of
-the companies that provides <A
-HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">commercial support</A> for ACE+TAO.<P>
+<LI> If it's a general question about how to use ACE, TAO, or CIAO
+feature we'll try to respond as time permits, though we will also rely
+on the experience of the open-source user community to field these
+types of questions, as well. You should first check out the <A
+HREf="http://www.theaceorb.com/faq/">online FAQ</A> to see if your
+question has already been answered. If you require consulting support
+for ACE, TAO, or CIAO, please contact one of the companies that
+provides <A
+HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">commercial
+support</A>.<P>
</UL>
-Naturally, we encourage other ACE+TAO users to continue to help
-provide fixes and advice in response to postings on the ACE and TAO
-mailing list. If you have a patch that fixes a problem you've found
-with our software here's the process for submitting it:
+Naturally, we encourage other ACE, TAO, and CIAO users to continue to
+help provide fixes and advice in response to postings on the mailing
+lists and newsgroup. If you have a patch that fixes a problem you've
+found with our software here's the process for submitting it:
<OL>
-<LI> Use the latest version of the ACE, i.e., what's available from <P>
+<LI> Use the latest contents of our CVS repository, i.e., what's available from <P>
<A HREF="http://cvs.doc.wustl.edu/">http://cvs.doc.wustl.edu/</A> <P>
@@ -139,17 +146,25 @@ with our software here's the process for submitting it:
<A HREF="http://deuce.doc.wustl.edu/bugzilla/index.cgi">http://deuce.doc.wustl.edu/bugzilla/index.cgi</A> <P>
- and send an email to the ACE mailing list or comp.soft-sys.ace newsgroup
- summarizing what the problem was and you've done to fix the problem,
- i.e., use the ChangeLog format. <P>
+ and send an email to the appropriate <A
+HREF="http://www.cs.wustl.edu/~schmidt/ACE-mail.html">mailing
+list(s)</A> and/or <A HREF="news:comp.soft-sys.ace">newsgroup</A>
+newsgroup summarizing what the problem was and you've done to fix the
+problem, i.e., use the <A HREF="../ChangeLog"</A>ChangeLog</A>
+format. <P>
<LI> Ideally, you could also create (or augment) a test program that
- validates your patch and integrate it into the ACE_ROOT/tests directory. <P>
-</OL>
-
-Please be sensitive to the fact that the core team is <EM>very</EM>
-busy so we simply don't have time to address problems reported by
-non-sponsors. <P>
+ validates your patch and integrate it into the <A
+HREF="../tests">ACE_ROOT/tests</A> directory. <P> </OL>
+
+Please be sensitive to the fact that the core <A
+HREF="http://www.dre.vanderbilt.edu/">DOC group</A> team is
+<EM>very</EM> busy, so we often don't have time to address problems
+reported by non-sponsors. If you'd like an immediate response, please
+contact <A HREF="mailto:schmidt@cs.wustl.edu">me</A> about becoming a
+sponsor or contact one of the companies that provides <A
+HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">
+commercial support</A> for ACE, TAO, and CIAO. <P>
<HR><P>
Back to the <A
diff --git a/docs/index.html b/docs/index.html
index e9d6971ac03..18de311d5c7 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -59,8 +59,8 @@ ask. <P>
<h3>Bug Reports</h3>
<ul>
- <li><a href="ACE-bug-process.html">ACE+TAO Bug Fixing Policies</a> - Our policies for
- handling bug reports.
+ <li><a href="ACE-bug-process.html">Bug Fixing Policies</a> - Our policies for
+ handling bug reports about ACE, TAO, and CIAO.
<li><a href="usage-bugzilla.html">Bug Tracking System</a> - Short description of our
Bugzilla bug tracking system.
</ul>
@@ -72,13 +72,14 @@ ask. <P>
<ul>
<li><a href="ACE-development-process.html">Development and Release Process</a> - The process we use
- to develop and release the ACE library.
+ to develop and release the ACE, TAO, and CIAO software.
<li><a href="CVS.html">Overview of CVS</a> - How to use the source
control system we use for ACE, TAO, CIAO, etc.
- <li><a href="ACE-guidelines.html">Style Guide</a> - How to write compliant ACE code.
+ <li><a href="ACE-guidelines.html">Style Guide</a> - How to write
+ compliant ACE, TOA, and CIAO code.
<li><a href="ACE-porting.html">Porting</a> - What to do to port to a new platform.
<li><a href="exceptions.html">Exception Macros</a> - How to use the ACE TRY
- macros properly.
+ macros properly (note that these macros are now deprecated).
</ul>