Documentation updates related to migration to github

* ACE/docs/ACE-bug-process.html: * ACE/docs/ACE-development-process.html: * ACE/docs/usage-bugzilla.html:
author: Johnny Willemsen <jwillemsen@remedy.nl> 2014-12-27 16:02:53 +0100
committer: Johnny Willemsen <jwillemsen@remedy.nl> 2014-12-27 16:02:53 +0100
commit: 06325909ca408a6f4720ef00e4a92b26302f8690 (patch)
tree: cdce804a2074233ded72dbd7422cb9232edb3386 /ACE
parent: 4042a8c5cade2138dc710023fd4854bea93549cc (diff)
download: ATCD-06325909ca408a6f4720ef00e4a92b26302f8690.tar.gz
3 files changed, 43 insertions, 41 deletions
diff --git a/ACE/docs/ACE-bug-process.html b/ACE/docs/ACE-bug-process.html
index 8145e2cf3e6..92bc7a2495d 100644
--- a/ACE/docs/ACE-bug-process.html
+++ b/ACE/docs/ACE-bug-process.html
@@ -1,15 +1,15 @@
 <!-- $Id$ -->
 
 <HTML>
-    <TITLE>ACE, TAO, and CIAO Bug Fixing Policies</TITLE>
+    <TITLE>ACE, TAO, CIAO and DAnCE Bug Fixing Policies</TITLE>
   <BODY text = "#000000" link="#000fff" vlink="#ff0f0f" bgcolor="#ffffff">
 
 <HR>
-<H3>ACE, TAO, and CIAO Bug Fixing Policies</H3>
+<H3>ACE, TAO, CIAO, and DAnCE Bug Fixing Policies</H3>
 
 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
+HREF="http://www.dre.vanderbilt.edu/TAO/">TAO</A>, <A
+HREF="http://www.dre.vanderbilt.edu/CIAO/">CIAO</A>, and DAnCE have grown in
 popularity the volume of mail on the <A
 HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-mail.html">mailing
 lists</A> and USENET newsgroup <A
@@ -26,7 +26,7 @@ traffic immediately.  Prompt bug fixes from the DOC group also
 discourage the creation of a larger community of <A
 HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-members.html">users</A> and
 <A
-HREF="www.dre.vanderbilt.edu/support.html">commercial
+HREF="http://www.dre.vanderbilt.edu/support.html">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>
 
@@ -47,7 +47,9 @@ lists</A> should be submitted using the appropriate bug report form in
 HREF="../TAO/PROBLEM-REPORT-FORM">$TAO_ROOT/PROBLEM-REPORT-FORM</A>
 (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
+(for CIAO), <A
+HREF="../TAO/DAnCE/PROBLEM-REPORT-FORM">$DAnCE_ROOT/PROBLEM-REPORT-FORM</A>
+(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: <P>
 
@@ -121,9 +123,8 @@ support</a> companies for ACE+TAO.<P>
     to <A
     HREF="mailto:taosupport@ociweb.com">taosupport@ociweb.com</A>.
     Likewise, if you find a problem with a version of TAO that was released by
-    <A HREF="http://www.prismtech.com">PrismTech</A> then please
-    report it to <A
-    HREF="mailto:technical-support@prismtech.com">technical-support@prismtech.com</A>.
+    <A HREF="http://www.microfocus.com">Micro Focus</A> 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. <P>
 
@@ -154,7 +155,14 @@ with our software here's the process for submitting it:
 
   <A HREF="https://github.com/DOCGroup/ATCD">https://github.com/DOCGroup/ATCD</A> <P>
 
-<LI> Create a ``unified diff'' and put this into Bugzilla at <P>
+<LI> 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  <A HREF="../tests">ACE_ROOT/tests</A>
+     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 <a href="https://help.github.com/articles/using-pull-requests/">pull request</a>.<P>
+
+<LI> Create a ``unified diff'' of all changs and put this into Bugzilla at <P>
 
   <A HREF="http://bugzilla.dre.vanderbilt.edu/">http://bugzilla.dre.vanderbilt.edu/</A> <P>
 
@@ -162,12 +170,7 @@ with our software here's the process for submitting it:
 HREF="http://www.dre.vanderbilt.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> Please create (or augment) a test program that
-  validates your patch and integrate it into the <A
-HREF="../tests">ACE_ROOT/tests</A> directory. <P>
+problem. <P>
 
 <LI> If your patch is for a platform/compiler that aren't part of our
 <A HREF="http://www.dre.vanderbilt.edu/scoreboard">autobuild
diff --git a/ACE/docs/ACE-development-process.html b/ACE/docs/ACE-development-process.html
index e3289a48d73..367b6b6bee2 100644
--- a/ACE/docs/ACE-development-process.html
+++ b/ACE/docs/ACE-development-process.html
@@ -12,14 +12,14 @@ vlink="#ff0f0f"
 bgcolor="#ffffff">
 
 <hr>
-<h3>The ACE+TAO Development and Release Process</h3>
+<h3>The ACE+TAO+CIAO+DAnCE Development and Release Process</h3>
 
 To improve the quality of our software and minimize development
 effort, we try to follow the structured development and release
 process described below.<p>
 
 An important concept to keep in mind is <em>risk</em>.  Before you
-commit <em>any</em> change to ACE+TAO, please consider the effects
+commit <em>any</em> 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
@@ -35,28 +35,29 @@ blocked for the duration of the broken build, the fix, and the
 rebuild.<p>
 
 <hr>
-<h3>The ACE+TAO+CIAO Development Process</h3>
+<h3>The ACE+TAO+CIAO+DAnCE Development Process</h3>
 
-The ACE+TAO+CIAO development process looks like:<p>
+The ACE+TAO+CIAO+DAnCE development process looks like:<p>
 <ol>
-  <li>Every change to ACE+TAO must have a bug report.  <em>Change</em>
+  <li>Every change to ACE+TAO+CIAO+DAnCE must have a bug report.  <em>Change</em>
     includes fixes, enhancements, updates, and so on.
   <li><a href="http://bugzilla.dre.vanderbilt.edu/">Create a
 bug report</a>.
   <li>Accept the bug report if you are going to implement the change.
-  <li>Implement the change in your workspace(s).
+  <li>Implement the change in your workspace(s) using a branch. Clearly
+    document each commit because that information is gathered into our
+    changelog
   <li>Test the change sufficiently to demonstrate that it both does
     what is intended, and doesn't break anything.  The test may be
-    as simple as building and running the ACE+TAO tests on at least two
+    as simple as building and running the ACE+TAO+CIAO+DAnCE tests on at least two
     platforms.
-    Or as complicated as rebuilding and test all of ACE+TAO on
+    Or as complicated as rebuilding and test all of ACE+TAO+CIAO+DAnCE on
     all platforms that we have.
-  <li>Create an appropriate ChangeLog entry.
-  <li>Commit the change using a ChangeLogTag commit message only when
+  <li>Merge the changes only to master when
     you are available the next 3 days to resolve any issues.
-    If you aren't available, hold your commit until you are available
+    If you aren't available, hold your merge until you are available
   <li>Respond to the requester of the change, if any.  Please do this
-    <em>after</em> committing your change.
+    <em>after</em> merging your change.
   <li>Make sure that the requester is listed in the THANKS file.
   <li>Update the bug report to indicate resolution.
   <li>Monitor the next round of build/tests for problems with your change.
@@ -174,7 +175,7 @@ commercial support</A> for ACE+TAO.<P>
 <H3>Contributions from the Open-Source Community</H3>
 <P>
 
-Over the years, ACE+TAO+CIAO have benefitted significantly from
+Over the years, ACE+TAO+CIAO have benefited significantly from
 contributions by <A
 HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-members.html">thousands</A>
 of developers in the open-source community.  To avoid fragmentation of
diff --git a/ACE/docs/usage-bugzilla.html b/ACE/docs/usage-bugzilla.html
index 9f5b362565e..47c8527915b 100644
--- a/ACE/docs/usage-bugzilla.html
+++ b/ACE/docs/usage-bugzilla.html
@@ -11,7 +11,7 @@
     <p>
       The
       <a href="http://www.dre.vanderbilt.edu">
-	Center for Distributed Object Computing</a> uses the
+  Center for Distributed Object Computing</a> uses the
       <a href="http://www.mozilla.org/projects/bugzilla/">Bugzilla</a>
       bug tracking system to keep track of existing problems and
       enhancement requests.
@@ -33,9 +33,9 @@
     <p>
       The bug tracking system is located at the following web site:
       <samp>
-	<a href="http://bugzilla.dre.vanderbilt.edu/">
-	  http://bugzilla.dre.vanderbilt.edu/
-	</a>
+  <a href="http://bugzilla.dre.vanderbilt.edu/">
+    http://bugzilla.dre.vanderbilt.edu/
+  </a>
       </samp>
 
     <p>
@@ -72,12 +72,12 @@
     <p>
     <blockquote>
       <samp>
-	<a href="http://www.mozilla.org/bugs">
-	  http://www.mozilla.org/bugs/
-	</a><br>
-	<a href="http://www.mozilla.org/quality/bug-writing-guidelines.html">
-	  http://www.mozilla.org/quality/bug-writing-guidelines.html
-	</a>
+  <a href="http://www.mozilla.org/bugs">
+    http://www.mozilla.org/bugs/
+  </a><br>
+  <a href="http://www.mozilla.org/quality/bug-writing-guidelines.html">
+    http://www.mozilla.org/quality/bug-writing-guidelines.html
+  </a>
       </samp>
     </blockquote>
 
@@ -88,8 +88,6 @@
       enhancement requests for ACE and TAO should be done at the
       Center for Distributed Object Computing's Bugzilla web site.
 
-
-
     <hr>
     <address><a href="mailto:ossama@dre.vanderbilt.edu">Ossama Othman</a></address>
 <!-- Created: Wed Aug 18 14:45:31 EDT 1999 -->
author	Johnny Willemsen <jwillemsen@remedy.nl>	2014-12-27 16:02:53 +0100
committer	Johnny Willemsen <jwillemsen@remedy.nl>	2014-12-27 16:02:53 +0100
commit	06325909ca408a6f4720ef00e4a92b26302f8690 (patch)
tree	cdce804a2074233ded72dbd7422cb9232edb3386 /ACE
parent	4042a8c5cade2138dc710023fd4854bea93549cc (diff)
download	ATCD-06325909ca408a6f4720ef00e4a92b26302f8690.tar.gz