diff options
| author | schmidt <douglascraigschmidt@users.noreply.github.com> | 2004-04-12 12:56:15 +0000 |
|---|---|---|
| committer | schmidt <douglascraigschmidt@users.noreply.github.com> | 2004-04-12 12:56:15 +0000 |
| commit | ad0a182956169be5af8e32e74458425109d04ee3 (patch) | |
| tree | c99cd32255edc2d907b0b979b26c43e98e371adf /docs | |
| parent | 8f4d59f5f9d25258333ef4e2d5ecc3999754c5c4 (diff) | |
| download | ATCD-ad0a182956169be5af8e32e74458425109d04ee3.tar.gz | |
ChangeLogTag:Thu Apr 1 15:40:55 2004 Douglas C. Schmidt <schmidt@cs.wustl.edu>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ACE-development-process.html | 23 |
1 files changed, 12 insertions, 11 deletions
diff --git a/docs/ACE-development-process.html b/docs/ACE-development-process.html index 61abd47999f..60278d9b5d8 100644 --- a/docs/ACE-development-process.html +++ b/docs/ACE-development-process.html @@ -155,17 +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> +The first beta following a major/minor release is called a +<EM>bug-fix-only</EM> (BFO) 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> |