ACE/docs/ACE-bug-process.html

   1 <!--  -->
   2
   3 <HTML>
   4     <TITLE>ACE, TAO, CIAO and DAnCE Bug Fixing Policies</TITLE>
   5   <BODY text = "#000000" link="#000fff" vlink="#ff0f0f" bgcolor="#ffffff">
   6
   7 <HR>
   8 <H3>ACE, TAO, CIAO, and DAnCE Bug Fixing Policies</H3>
   9
  10 As <A HREF="https://www.dre.vanderbilt.edu/ACE/">ACE</A>, <A
  11 HREF="https://www.dre.vanderbilt.edu/TAO/">TAO</A>, <A
  12 HREF="https://www.dre.vanderbilt.edu/CIAO/">CIAO</A>, and DAnCE have grown in
  13 popularity the volume of mail on the <A
  14 HREF="https://www.dre.vanderbilt.edu/~schmidt/ACE-mail.html">mailing
  15 lists</A> has grown
  16 considerably.  While this increase is healthy, and a natural
  17 consequence of the larger number of ACE, TAO, and CIAO users, it is
  18 straining the resources of the researchers in the <A
  19 HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-members-i.html">DOC
  20 group</A> at Washington
  21 University, UC Irvine, and <A
  22 HREF="https://www.dre.vanderbilt.edu">ISIS</A> to respond to all the
  23 traffic immediately.  Prompt bug fixes from the DOC group also
  24 discourage the creation of a larger community of <A
  25 HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-members.html">users</A> and
  26 <A
  27 HREF="http://www.dre.vanderbilt.edu/support.html">commercial
  28 support companies</A> who have deep knowledge of how ACE, TAO, and
  29 CIAO work and can help provide bug fixes and new features. <P>
  30
  31 <HR>
  32 <H3>Process for Reporting a Bug</H3>
  33
  34 To ensure the continued growth and maturation of ACE, TAO, and CIAO,
  35 and to allow the user and vendor communities to evolve, please make it
  36 a point to abide by the following policies:
  37
  38 <UL>
  39
  40 <LI> All bug reports to the  <A
  41 https://github.com/DOCGroup/ACE_TAO">github project
  42 lists</A> should be submitted using the appropriate bug report form in
  43 <A HREF="../PROBLEM-REPORT-FORM">$ACE_ROOT/PROBLEM-REPORT-FORM</A>
  44 (for ACE), <A
  45 HREF="../TAO/PROBLEM-REPORT-FORM">$TAO_ROOT/PROBLEM-REPORT-FORM</A>
  46 (for TAO), <A
  47 HREF="../TAO/CIAO/PROBLEM-REPORT-FORM">$CIAO_ROOT/PROBLEM-REPORT-FORM</A>
  48 (for CIAO), <A
  49 HREF="../TAO/DAnCE/PROBLEM-REPORT-FORM">$DAnCE_ROOT/PROBLEM-REPORT-FORM</A>
  50 (for DAnCE).  Please use these forms since bug reports that are not
  51 submitted in this form are likely to fall through the cracks.  Here is
  52 our policy for addressing these bug reports: <P>
  53
  54 <OL>
  55
  56 <LI> If a report is from someone <A
  57 HREF="https://www.dre.vanderbilt.edu/~schmidt/ACE-sponsors.html">sponsoring</A>
  58 our work we will respond to it in a very timely manner.  Please
  59 contact <A HREF="mailto:schmidt@dre.vanderbilt.edu">me</A> if you'd
  60 like to become a sponsor. <P>
  61
  62 <LI> If it's a bug report that pertains to the latest release and it
  63 also contains a fix we will try to apply this in a timely manner.  In
  64 general, people who submit good bug reports with fixes tend to get
  65 much better help from the core DOC group team, irrespective of whether
  66 they are sponsors or not since they are helping our overall effort
  67 move ahead. <P>
  68
  69 <LI> If it's a bug report for the latest release that prevents ACE,
  70 TAO, or CIAO from working on a popular platform used by ourselves or
  71 our sponsors we'll try to fix it as time permits. <P>
  72
  73 </OL>
  74
  75 <LI> You should also consider entering your bug report into a <A
  76 HREF="https://github.com/DOCGroup/ACE_TAO">github </A> issue
  77 so that it's archived for future processing.  As usual,
  78 we try to address these bugs as time permits, but may not get to them
  79 for a while unless it affects our work or the work of our
  80 sponsors. <P>
  81
  82 We encourage bug reports for those without support to be posted
  83 initially to the <A
  84 HREF="https://github.com/DOCGroup/ACE_TAO">github issues or discussions</A>.
  85 <P>
  86
  87 <LI> While the core DOC group development team participates on github
  88 , we cannot response to all postings.  Therefore, if you
  89 post something and don't get a reply, please do the following:<P>
  90
  91 <UL>
  92 <LI> When you haven't received a reply this probably means
  93   that either no one knows the answer or no one has time to answer it.
  94   As always, if you need more predictable help please contact one of
  95   <A
  96 HREF="http://www.dre.vanderbilt.edu/support.html">commercial
  97 support</a> companies for ACE+TAO.<P>
  98
  99 </UL>
 100
 101 <LI> If you find a problem with a version of TAO that was released by
 102     <A HREF="http://www.theaceorb.com/">OCI</A> then please report it
 103     to <A
 104     HREF="mailto:taosupport@ociweb.com">taosupport@ociweb.com</A>.
 105     Likewise, if you find a problem with a version of TAO that was released by
 106     <A HREF="http://www.microfocus.com">Micro Focus</A> then please
 107     report it to MicroFocus.
 108     Their versions of TAO are different from the DOC group's
 109     version of TAO and thus they provide their own support. <P>
 110
 111 <LI> If it's a general question about how to use ACE, TAO, or CIAO
 112 feature we'll try to respond as time permits, though we will also rely
 113 on the experience of the open-source user community to field these
 114 types of questions, as well.  You should first check out the <A
 115 HREf="http://www.theaceorb.com/faq/">online FAQ</A> or
 116 <A HREF="https://www.remedy.nl/opensource/corbapg.html">CORBA Programmers Guide</A>
 117 to see if your
 118 question has already been answered.  If you require consulting support
 119 for ACE, TAO, or CIAO, please contact one of the companies that
 120 provides <A
 121 HREF="http://www.dre.vanderbilt.edu/support.html">commercial
 122 support</A>.<P>
 123
 124 </UL>
 125
 126 <HR>
 127 <H3>Process for Submitting a Bug Fix</H3>
 128
 129 We encourage other ACE, TAO, and CIAO users to continue to help
 130 provide fixes and advice in response to github issues and discussions.
 131 If you have a patch that fixes a problem you've found
 132 with our software here's the process for submitting it:
 133
 134 <OL>
 135 <LI> Use the latest contents of git repository, i.e.,
 136      what's available from <P>
 137
 138   <A HREF="https://github.com/DOCGroup/ACE_TAO">https://github.com/DOCGroup/ACE_TAO</A> <P>
 139
 140 <LI> Create a fork of the ATCD repository and prepare your fixes including documentation
 141      changes and automated unit tests. For any change in ACE create (or augment) a test program
 142      that validates your patch and integrate it into the  <A HREF="../tests">ACE_ROOT/tests</A>
 143      directory. Clearly document each commit because that information
 144      will end up in the ATCD ChangeLog. When you have tested your changes at least on Windows
 145      and Linux prepare a <a href="https://help.github.com/articles/using-pull-requests/">pull request</a>.<P>
 146
 147 <LI> Create a github pull reuquest at <P>
 148
 149   <A HREF="https://github.com/DOCGroup/ACE_TAO">https://github.com/DOCGroup/ACE_TAO</A> <P>
 150
 151 <LI> If your patch is for a platform/compiler that aren't part of our
 152 <A HREF="http://www.dre.vanderbilt.edu/scoreboard">autobuild
 153 scoreboard</A> please consider contributing one or more autobuilds
 154 that can be used to keep track of changes to your platform/compiler
 155 combination and ensure things continue to work as the ACE+TAO source
 156 code evolves. <P>
 157
 158 <LI> By submitting bug fixes submitters acknowledge that they have the
 159 right to do so, that any such submissions are given freely and
 160 unreservedly, and that they waive any claims to copyright or
 161 ownership.  In addition, submitters acknowledge that any such
 162 submission might become part of the copyright maintained on the
 163 overall body of code that comprises the DOC software.  By making a bug
 164 fix submission, submitter agree to these terms.  Moreover, submitters
 165 acknowledge that the incorporation or modification of such submissions
 166 is entirely at the discretion of the moderators of the open-source DOC
 167 software projects or their designees. <P>
 168
 169 </OL>
 170
 171 Please be sensitive to the fact that the core <A
 172 HREF="http://www.dre.vanderbilt.edu/">DOC group</A> team is
 173 <EM>very</EM> busy, so we often don't have time to address problems
 174 reported by non-sponsors.  If you'd like an immediate response, please
 175 contact <A HREF="mailto:schmidt@dre.vanderbilt.edu">me</A> about
 176 becoming a sponsor or contact one of the companies that provides <A
 177 HREF="http://www.dre.vanderbilt.edu/support.html">
 178 commercial support</A> for ACE, TAO, and CIAO. <P>
 179
 180 <HR><P>
 181 Back to the <A
 182 HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE.html">ACE</A> page.<BR>
 183 Back to <A HREF="index.html">ACE Documentation Home</A>.
 184
 185 <!--#include virtual="/~schmidt/cgi-sig.html" -->
 186 </BODY>
 187 </HTML>