An important concept to keep in mind is risk. Before you commit any change to ACE+TAO+CIAO+DAnCE, please consider the effects that it will have. Could it possibly cause a build failure, on any platform? Could it possibly cause different run-time behavior? And so on. If so, it is your responsibility to adequately build and test with the change, in order to verify that it has no unintended effects.
Please keep in mind the cost of committing a mistake. It may take you only a few seconds to fix, but its cost to the group may be much larger. With our large group, workspace updates and builds are likely to happen at any time. If one break, it can take hours to rebuild it. And each developer that was waiting for a successful build would be blocked for the duration of the broken build, the fix, and the rebuild.
A bug should typically follow this life cycle:
|Owner:||Reproduces problem - if it needs a new test, write it and
put it in the regression tests.
If it can't be reproduced, set to Resolved/CANT_FIND.
If it's a duplicate, set it to Resolved/DUPLICATE. Fix code, commit changes, set to Resolved.
|Submitter:||Tests it again; set to Verified (pass) or Reopened (fail)|
|Owner:||After next release is done, re-test; sets to Closed or Reopened.|
At all times, we'll have a build czar. The role may be shared by multiple people. The build czar is responsible for ensuring that the next kits are clean, i.e., it builds and runs cleanly on all platforms. The status of all ACE+TAO+CIAO+DAnCE builds is tracked automatically online.
A comprehensive summary of the build czar's role is available here. This role is briefly summarized below:
Minor releases of ACE+TAO+CIAO+DAnCE occur periodically, typically twice a year. Minor releases have two-digit numbers, e.g., 5.3. Major releases are released infrequently, typically once a year. Major releases are 1-digit numbers, e.g.,5, that include substantially new functionality. Both major and minor releases are carefully tested on all platforms the ACE+TAO run on. In particular, we do not put out major or minor releases of ACE+TAO+CIAO+DAnCE until all the compilations and regression tests work successful on all the platform we support.
Between major/minor releases, we release micro releases periodically, e.g., 3-4 times per year, so that ACE+TAO+CIAO+DAnCE users can download and test our latest work in progress. ACE+TAO+CIAO+DAnCE micro release kits have three-digit numbers, e.g., 5.3.1. Micro releases often contain important fixes that aren't in the major/minor releases and will compile cleanly and pass most tests on most platforms. They are not, however, necessarily concerned with ensuring API compatibilities between micro releases, e.g., new features may be changed or removed between the micro releases.
Over the years, ACE+TAO+CIAO have benefited significantly from contributions by thousands of developers in the open-source community. To avoid fragmentation of the code base, by submitting comments, suggestions, code, code snippets, techniques (including that of usage) and algorithms (collectively ``Submissions''), 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 open-source DOC Group software. By making a 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.