ACE, TAO, CIAO and DAnCE Bug Fixing Policies

### ACE, TAO, CIAO, and DAnCE Bug Fixing Policies

As ACE, TAO, CIAO, and DAnCE have grown in popularity the volume of mail on the mailing lists has grown considerably. While this increase is healthy, and a natural consequence of the larger number of ACE, TAO, and CIAO users, it is straining the resources of the researchers in the DOC group at Washington University, UC Irvine, and ISIS to respond to all the traffic immediately. Prompt bug fixes from the DOC group also discourage the creation of a larger community of users and commercial support companies who have deep knowledge of how ACE, TAO, and CIAO work and can help provide bug fixes and new features.

### Process for Reporting a Bug

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:

- All bug reports to the mailing lists should be submitted using the appropriate bug report form in $ACE_ROOT/PROBLEM-REPORT-FORM (for ACE), $TAO_ROOT/PROBLEM-REPORT-FORM (for TAO), $CIAO_ROOT/PROBLEM-REPORT-FORM (for CIAO), $DAnCE_ROOT/PROBLEM-REPORT-FORM (for DAnCE). 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:

  1. If a report is from someone sponsoring our work we will respond to it in a very timely manner. Please contact me if you'd like to become a sponsor.

  2. If it's a bug report that pertains to the latest release and it also contains 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.

  3. If it's a bug report for the latest release that prevents ACE, TAO, or CIAO from working on a popular platform used by ourselves or our sponsors we'll try to fix it as time permits.

- You should also consider entering your bug report into a github issue 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.

  We encourage bug reports for those without support to be posted initially to the ACE users (ace-users@list.isis.vanderbilt.edu), TAO users (tao-users@list.isis.vanderbilt.edu), and CIAO users (ciao-users@list.isis.vanderbilt.edu) mailing lists, where the open-source user community may already have developed, or have an interest in developing, a solution.

- 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:

  - Check to see whether your posting made it to the list through the list archives, which you can see by checking out the list archive to see if your posting is visible.

  - If it's not visible, please make sure you're subscribed to the mailing list(s) you sent the report to since we have a "members only" posting requirement to minimize spam.

  - 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 commercial support companies for ACE+TAO.

- If you find a problem with a version of TAO that was released by OCI then please report it to taosupport@ociweb.com. Likewise, if you find a problem with a version of TAO that was released by Micro Focus then please report it to MicroFocus. Their versions of TAO are different from the DOC group's version of TAO and thus they provide their own support.

- 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 online FAQ or CORBA Programmers Guide 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 commercial support.

### Process for Submitting a Bug Fix

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:

1. Use the latest contents of git repository, i.e., what's available from

   https://github.com/DOCGroup/ACE_TAO

2. Create a fork of the ATCD repository and prepare your fixes including documentation changes and automated unit tests. For any change in ACE create (or augment) a test program that validates your patch and integrate it into the ACE_ROOT/tests directory. Clearly document each commit because that information will end up in the ATCD ChangeLog. When you have tested your changes at least on Windows and Linux prepare a pull request.

3. Create a ``unified diff'' of all changes and put this into a github issue at

   https://github.com/DOCGroup/ACE_TAO

   and send an email to the appropriate mailing list(s) summarizing what the problem was and you've done to fix the problem.

4. If your patch is for a platform/compiler that aren't part of our autobuild scoreboard please consider contributing one or more autobuilds that can be used to keep track of changes to your platform/compiler combination and ensure things continue to work as the ACE+TAO source code evolves.

5. By submitting bug fixes submitters acknowledge that they have the right to do so, that any such submissions are given freely and unreservedly, and that they waive any claims to copyright or ownership. In addition, submitters acknowledge that any such submission might become part of the copyright maintained on the overall body of code that comprises the DOC software. By making a bug fix submission, submitter agree to these terms. Moreover, submitters acknowledge that the incorporation or modification of such submissions is entirely at the discretion of the moderators of the open-source DOC software projects or their designees.

Please be sensitive to the fact that the core DOC group team is very busy, so we often don't have time to address problems reported by non-sponsors. If you'd like an immediate response, please contact me about becoming a sponsor or contact one of the companies that provides commercial support for ACE, TAO, and CIAO.

Back to the ACE page.
Back to ACE Documentation Home.