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:

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 github issues and discussions. 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

  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 github pull reuquest at

  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.