summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorbala <balanatarajan@users.noreply.github.com>2004-01-16 02:34:28 +0000
committerbala <balanatarajan@users.noreply.github.com>2004-01-16 02:34:28 +0000
commita3b2ac9899f5383efba1a65ca66a8a35fa94bf6c (patch)
tree3d5d5ef6b6fa1eab56c7c8de16f868e15228d8d5 /docs
parentf22292953e86ef072f44765fb5494dc3e856e496 (diff)
downloadATCD-a3b2ac9899f5383efba1a65ca66a8a35fa94bf6c.tar.gz
ChangeLogTag:Thu Jan 15 20:33:09 2004 Balachandran Natarajan <bala@dre.vanderbilt.edu>
Diffstat (limited to 'docs')
-rw-r--r--docs/ACE-development-process.html12
1 files changed, 12 insertions, 0 deletions
diff --git a/docs/ACE-development-process.html b/docs/ACE-development-process.html
index dd9dee82747..61abd47999f 100644
--- a/docs/ACE-development-process.html
+++ b/docs/ACE-development-process.html
@@ -155,6 +155,18 @@ for TAO commercial support or <A
HREF="http://www.riverace.com/">Riverace</A> for ACE commercial
support. <P>
+The first beta following a major/minor release is called a <EM> Bug
+Fix Only (BFO) </EM> beta. As the name implies this beta will have
+only fixes for the major or minor releases just made. Types of fixes
+and checkins that are allowed to go in for the BFO include, bug fixes
+in the implementation, fixes to the build systems like Makefiles,
+project files, and MPC files, adding new tests and examples, fixes to
+the documentation etc. Fixes that are definitely not allowed include,
+changes to the public interface, refactoring implementations, removing
+files from the repository, adding new files into the repository
+etc. The idea is to allow commercial support vendors to stabilize the
+major or minor release for their product offerings. <p>
+
<hr><p>
<font size=-1>
Last modified