Updated links and documentation to point to github and latest pagest from Doug

    * ACE/ACE-INSTALL.html:
    * ACE/docs/ACE-bug-process.html:
    * ACE/docs/ACE-development-process.html:
    * ACE/docs/Download.html:
    * ACE/docs/bczar/bczar.html:
    * TAO/TAO-INSTALL.html:

5 files changed, 41 insertions, 55 deletions

diff --git a/ACE/ACE-INSTALL.html b/ACE/ACE-INSTALL.html
index 8ebe91000e3..a6f4e4b34b8 100644
--- a/ACE/ACE-INSTALL.html
+++ b/ACE/ACE-INSTALL.html
@@ -98,7 +98,7 @@ to provide build results. Members of the ACE community that maintain ACE on
 platforms not maintained by the DOC group, Riverace, OCI, or Remedy IT are
 encouraged to provide build and regression test results for the scoreboard
 to ensure that all in-use platforms are represented.
-See the <a href="https://svn.dre.vanderbilt.edu/viewvc/autobuild/trunk/README?revision=HEAD" target="_blank">autobuild README</a> for more information about
+See the <a href="https://raw.githubusercontent.com/DOCGroup/autobuild/master/README" target="_blank">autobuild README</a> for more information about
 how to set up a build; contact one of the above groups to inquire about how
 to get your build results recorded on the scoreboard.</p>
 <p>Because older
@@ -2628,14 +2628,14 @@ You need to do one of the following:
 <li>If you have already obtained MPC, either move it underneath the
 ACE_wrappers directory or set your MPC_ROOT environment variable to point
 to the full path of MPC.</li>
-<li>Check out MPC from the DOC Group subversion repository
+<li>Check out MPC from the DOC Group git repository
 and set your MPC_ROOT environment variable.</li>
 </ol>
 
 You can check
-out MPC from the doc_group subversion server using the following command.
+out MPC from the DOCGroup git repository using the following command.
 
-<pre>svn co svn://svn.dre.vanderbilt.edu/DOC/MPC/trunk MPC
+<pre>git clone https://github.com/DOCGroup/MPC.git MPC
 </pre>
 
 The <A HREF="MPC/docs/README">README</A> and <A HREF="MPC/docs/USAGE">USAGE</A> files in the MPC/docs directory are an up-to-date
@@ -2929,26 +2929,18 @@ show_uninit        Lists all uninitialized in object files built for
 </pre>
 
 </p><hr><p>
-</p><h2><a name="power">Building from Subversion (anonymous access)</a></h2>
-If users are building from our <a href="https://svn.dre.vanderbilt.edu/viewvc/Middleware/trunk/">Subversion repository</a> the
+</p><h2><a name="power">Building from git</a></h2>
+If users are building from our <a href="https://github.com/DOCGroup/ATCD">Git repository</a> the
 GNUmakefiles, and project files for building on various platforms will
-not be available.  Subversion users are expected to <a href="#generate_using_mpc">generate them</a>
-using <a href="https://svn.dre.vanderbilt.edu/viewvc/MPC/trunk/docs/README?revision=HEAD">MPC</a> before building ACE, TAO or
+not be available.  Git users are expected to <a href="#generate_using_mpc">generate them</a>
+using <a href="https://raw.githubusercontent.com/DOCGroup/MPC/master/docs/README">MPC</a> before building ACE, TAO or
 CIAO. We point out some suggestions below to get bootstrapped
 quickly.
 
 <ul>
-  <li>You can checkout different subsets from the Subversion repository.
+  <li>You can clone all code easily from our git repository.
   <ul>
-  <li>To checkout ACE with MPC:<p>
-  <code>svn co svn://svn.dre.vanderbilt.edu/DOC/Middleware/sets-anon/ACE .</code>
-  </li>
-  <li>To checkout ACE+TAO with MPC:<p>
-  <code>svn co svn://svn.dre.vanderbilt.edu/DOC/Middleware/sets-anon/ACE+TAO .</code>
-  </li>
-  <li>To checkout ACE+TAO+CIAO with MPC:<p>
-  <code>svn co svn://svn.dre.vanderbilt.edu/DOC/Middleware/sets-anon/ACE+TAO+CIAO .</code>
-  </li>
+  <code>git clone https://github.com/DOCGroup/ATCD.git</code>
   </ul>
   </p></li><li>Please make sure that you have <a href="http://www.perl.org/">
   perl</a> installed, preferably perl
diff --git a/ACE/docs/ACE-bug-process.html b/ACE/docs/ACE-bug-process.html
index 5607fc6e95e..9d84233fc53 100644
--- a/ACE/docs/ACE-bug-process.html
+++ b/ACE/docs/ACE-bug-process.html
@@ -111,7 +111,7 @@ to the mailing
   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
   <A
-HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">commercial
+HREF="http://www.dre.vanderbilt.edu/support.html">commercial
 support</a> companies for ACE+TAO.<P>
 
 </UL>
@@ -135,7 +135,7 @@ HREf="http://www.theaceorb.com/faq/">online FAQ</A> 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 <A
-HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">commercial
+HREF="http://www.dre.vanderbilt.edu/support.html">commercial
 support</A>.<P>
 
 </UL>
@@ -149,10 +149,10 @@ and newsgroup.  If you have a patch that fixes a problem you've found
 with our software here's the process for submitting it:
 
 <OL>
-<LI> Use the latest contents of subversion repository, i.e.,
+<LI> Use the latest contents of git repository, i.e.,
      what's available from <P>
 
-  <A HREF="https://svn.dre.vanderbilt.edu/viewvc/Middleware/trunk/">https://svn.dre.vanderbilt.edu/</A> <P>
+  <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>
 
@@ -195,7 +195,7 @@ HREF="http://www.dre.vanderbilt.edu/">DOC group</A> team is
 reported by non-sponsors.  If you'd like an immediate response, please
 contact <A HREF="mailto:schmidt@dre.vanderbilt.edu">me</A> about
 becoming a sponsor or contact one of the companies that provides <A
-HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">
+HREF="http://www.dre.vanderbilt.edu/support.html">
 commercial support</A> for ACE, TAO, and CIAO. <P>
 
 <HR><P>
diff --git a/ACE/docs/ACE-development-process.html b/ACE/docs/ACE-development-process.html
index e964c1a4037..a9a294b0512 100644
--- a/ACE/docs/ACE-development-process.html
+++ b/ACE/docs/ACE-development-process.html
@@ -47,19 +47,19 @@ bug report</a>.
   <li>Implement the change in your workspace(s).
   <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 tests on at least two
     platforms.
     Or as complicated as rebuilding and test all of ACE+TAO on
     all platforms that we have.
   <li>Create an appropriate ChangeLog entry.
-  <li>Commit the change using a ChangeLogTag commit message only when 
-    you are available the next 3 days to resolve any issues. 
+  <li>Commit the change using a ChangeLogTag commit message only when
+    you are available the next 3 days to resolve any issues.
     If you aren't available, hold your commit until you are available
   <li>Respond to the requester of the change, if any.  Please do this
     <em>after</em> committing 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. 
+  <li>Monitor the next round of build/tests for problems with your change.
    Because there are slow systems it can take up to 4 days to get all builds done.
   <li>Respond immediately to reports of problems with your changes.
 </ol>
@@ -137,7 +137,7 @@ Right Thing[TM] to do.<p>
 Minor releases of ACE+TAO+CIAO+DAnCE occur periodically, typically twice a
 year. Minor releases have two-digit numbers, <EM>e.g.,</EM> 5.3.
 Major releases are released infrequently, typically once a year.
-Major releases are 1-digit numbers, <EM>e.g.,</EM>5, that include 
+Major releases are 1-digit numbers, <EM>e.g.,</EM>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
@@ -167,7 +167,7 @@ into the repository, etc. The idea is to allow commercial support
 vendors to stabilize the major or minor release for their product
 offerings.  As always, if you require 100% predictable stability and
 support, please contact one of the companies that provides <A
-HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">
+HREF="http://www.dre.vanderbilt.edu/support.html">
 commercial support</A> for ACE+TAO.<P>
 
 <p><hr>
@@ -194,7 +194,7 @@ designees.
 
 <hr><p>
   <font size=-1>
-    Last modified 
+    Last modified
 <!--#echo var="LAST_MODIFIED" -->.<p>
   </font><hr>
 
diff --git a/ACE/docs/Download.html b/ACE/docs/Download.html
index 96ca17e46cf..900fff7b8fd 100644
--- a/ACE/docs/Download.html
+++ b/ACE/docs/Download.html
@@ -517,7 +517,7 @@ the links below to download it.
       via the web</A>.
   </LI>
   <li>ACE+TAO+CIAO+DAnCE source code may be obtained from the
-    <a href="https://svn.dre.vanderbilt.edu/viewvc/Middleware/trunk/ACE/ACE-INSTALL.html?revision=HEAD#power">Subversion repository</a>.</li>
+    <a href="http://htmlpreview.github.com/?https://github.com/DOCGroup/ATCD/blob/master/ACE/ACE-INSTALL.html#power">Git repository</a>.</li>
   <LI>Commercially supported versions of ACE+TAO+CIAO+DAnCE are available from
     <A HREF="http://www.dre.vanderbilt.edu/support.html">several companies</A>.
   <LI>RPMs for CentOS, Fedora, Mandriva, RHEL, SLE, and OpenSuSE are available from the
diff --git a/ACE/docs/bczar/bczar.html b/ACE/docs/bczar/bczar.html
index 3066eab23b0..4ecc7c0300f 100644
--- a/ACE/docs/bczar/bczar.html
+++ b/ACE/docs/bczar/bczar.html
@@ -55,7 +55,7 @@
     </P>
     <P>
       The Build Czar is empowered to set up more builds on his own for his
-      convenience. This <a href="https://svn.dre.vanderbilt.edu/viewvc/autobuild/trunk/README?revision=HEAD">
+      convenience. This <a href="https://raw.githubusercontent.com/DOCGroup/autobuild/master/README">
         page </a>has a step by step instructions on how to do that.
     </P>
     <P>
@@ -63,7 +63,7 @@
       of the scoreboard.
     </P>
     <p>Pro-active involvement by the build czar is necessary. Being a pro-active
-      build czar requires monitoring the subversion archive carefully and responding
+      build czar requires monitoring the git repository carefully and responding
       quickly to suspected changes to keep the repo stays stable.</p>
     <p>After an email from the Coverity scan project check the Coverity project and
        check that there are no new errors reported. If so, contact the person who
@@ -113,7 +113,7 @@
           </ul>
           or on OpenSuSE
           <ul>
-            <li><code>zypper install perl subversion screen python-pysvn automake doxygen bzip2 tar gzip openssh graphviz zip libtool python-gitpython</code></li>
+            <li><code>zypper install perl screen python-pysvn automake doxygen bzip2 tar gzip openssh graphviz zip libtool python-gitpython</code></li>
             <li><code>zypper update</code></li>
           </ul>
           If you want to perform a full build with qt support, than run:
@@ -139,11 +139,9 @@
             Checkout like this:
             <ul>
               <li>
-                <code>svn co --username &lt;your user id&gt;
-                https://svn.dre.vanderbilt.edu/DOC/Middleware/trunk DOC_ROOT</code></li>
+                <code>git clone https://github.com/DOCGroup/ATCD.git ATCD</code></li>
               <li>
-                <code>svn co --username &lt;your user id&gt;
-                https://svn.dre.vanderbilt.edu/DOC/MPC/trunk DOC_ROOT/ACE/MPC</code></li>
+                <code>git clone https://github.com/DOCGroup/ATCD.git MPC</code></li>
             </ul>
         </ul>
         <li>
@@ -165,7 +163,7 @@
         </li>
         <li>
           Tag the release by executing<br>
-          <code>ACE/bin/make_release.py --beta --update --tag</code><br>
+          <code>ACE/bin/make_release.py --beta --update --tag -- push</code><br>
           This will only take a couple minutes to complete and once done successfully,
           you can carry on with BOTH creating the kits and generating the doxygen
           documentation in parallel. NOTE that <code>--beta</code> should be replaced
@@ -176,7 +174,7 @@
         <br>
         In the <em>EXTREMELY</em> unlikely event that something goes wrong during the <em>
           tagging</em> of the repo, the following files must be returned to the state
-        they were in before the release process started and then checked back into SVN:<br>
+        they were in before the release process started and then checked back into git:<br>
         <ul>
           <code>
             <li>
@@ -210,9 +208,8 @@
     ACE+TAO+CIAO-X_Y_Z (where X is the ACE Major version number, and Y & Z are the
     Minor and Beta release numbers of the release that is to be restarted).<p>
       E.g.:<br>
-      <code>svn rm
-        https://svn.dre.vanderbilt.edu/DOC/Middleware/tags/ACE+TAO+CIAO-X_Y_Z<br />
-        svn rm https://svn.dre.vanderbilt.edu/DOC/MPC/tags/ACE+TAO+CIAO-X_Y_Z<br />
+      <code>cd ATCD && git tag -d ACE+TAO+CIAO-X_Y_Z<br />
+        cd MPC && git tag -d ACE+TAO+CIAO-X_Y_Z<br />
       </code>
       <br>
       Note that this <em>only</em> needs to be done if the <em>tagging</em> fails. If
@@ -288,19 +285,16 @@
             version number being released e.g. 5_6_7)
             <br>
             <code>svn co
-              git clone svn://svn.dre.vanderbilt.edu/DOC/Middleware/tags/ACE+TAO+CIAO-X_Y_Z/ACE ACE_wrappers<br>
-              svn co svn://svn.dre.vanderbilt.edu/DOC/Middleware/tags/ACE+TAO+CIAO-X_Y_Z/TAO ACE_wrappers/TAO<br>
-              svn co svn://svn.dre.vanderbilt.edu/DOC/Middleware/tags/ACE+TAO+CIAO-X_Y_Z/CIAO ACE_wrappers/TAO/CIAO<br>
-              svn co svn://svn.dre.vanderbilt.edu/DOC/Middleware/tags/ACE+TAO+CIAO-X_Y_Z/DAnCE ACE_wrappers/TAO/DAnCE</code>
+              git clone https://github.com/DOCGroup/ATCD.git --depth 1 --branch ACE+TAO+CIAO-6_3_1 ATCD<br>
           </li>
-          <li>Change to the ACE_wrappers directory using <br>
-          cd ACE_wrappers</li>
+          <li>Change to the ATCD directory using <br>
+          cd ATCD</li>
           <li>
             Set the needed environment variables using<br>
-            <code>export ACE_ROOT=$PWD</code><br>
-        <code>export TAO_ROOT=$ACE_ROOT/TAO</code><br>
-        <code>export CIAO_ROOT=$TAO_ROOT/CIAO</code><br>
-        <code>export DANCE_ROOT=$TAO_ROOT/DAnCE</code><br>
+            <code>export ACE_ROOT=$PWD/ACE</code><br>
+        <code>export TAO_ROOT=$PWD/TAO</code><br>
+        <code>export CIAO_ROOT=$PWD/CIAO</code><br>
+        <code>export DANCE_ROOT=$PWD/DAnCE</code><br>
         <code>export DDS_ROOT=</code><br></li>
           <li>
             Check the doxygen version at the shell by executing the command:<br>
@@ -322,7 +316,7 @@
         rm -rf doxygen<br>
         mkdir doxygen<br>
         cd doxygen<br>
-        git clone https://github.com/DOCGroup/ATCD.git ATCD
+        git clone https://github.com/DOCGroup/ATCD.git --depth 1 --branch ACE+TAO+CIAO-6_3_1 ATCD
         cd ATCD<br>
         export ACE_ROOT=$PWD/ACE<br>
         export TAO_ROOT=$PWD/TAO<br>
@@ -340,7 +334,7 @@
           <li>Get from bugzilla the bugs fixed. Use the following
               <a href="http://bugzilla.dre.vanderbilt.edu/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ACE&product=CIAO&product=CoSMIC&product=MPC&product=OpenDDS&product=TAO&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailreporter2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2010-07-04&chfieldto=Now&chfield=resolution&chfieldvalue=FIXED&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">query</a> as start query and update the start date.</li>
           <li>
-            Let <a href="mailto:schmidt@cs.wustl.edu">Doug Schmidt</a> review these before
+            Let <a href="mailto:d.schmidt@vanderbilt.edu">Doug Schmidt</a> review these before
             you do anything with them.</li></ul>
 
       <li>