summaryrefslogtreecommitdiff
path: root/ACE/docs/ACE-development-process.html
diff options
context:
space:
mode:
authorJohnny Willemsen <jwillemsen@remedy.nl>2014-12-07 15:26:14 +0100
committerJohnny Willemsen <jwillemsen@remedy.nl>2014-12-07 15:26:14 +0100
commit1c10f8ec74aca70417c54040ecc7f27dffd46511 (patch)
treecc4da051a6fcdb74da07e965f21921cbb403cb69 /ACE/docs/ACE-development-process.html
parentdf687d078bd9b23ceab144fe287c17f412c2130d (diff)
downloadATCD-1c10f8ec74aca70417c54040ecc7f27dffd46511.tar.gz
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:
Diffstat (limited to 'ACE/docs/ACE-development-process.html')
-rw-r--r--ACE/docs/ACE-development-process.html14
1 files changed, 7 insertions, 7 deletions
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>