diff options
Diffstat (limited to 'ACE/docs/ACE-development-process.html')
| -rw-r--r-- | ACE/docs/ACE-development-process.html | 16 |
1 files changed, 0 insertions, 16 deletions
diff --git a/ACE/docs/ACE-development-process.html b/ACE/docs/ACE-development-process.html index 4e25fcb84f2..7d980d3fd62 100644 --- a/ACE/docs/ACE-development-process.html +++ b/ACE/docs/ACE-development-process.html @@ -155,22 +155,6 @@ platforms. They are not, however, necessarily concerned with ensuring API compatibilities between micro releases, <EM>e.g.,</EM> new features may be changed or removed between the micro releases. <P> -The first micro release following a major/minor release is called the -<EM>bug-fix-only</EM> (BFO) micro release. As the name implies, this -micro release only has fixes for the most recent major/minor releases. -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. As always, if you require 100% predictable stability and -support, please contact one of the companies that provides <A -HREF="http://www.dre.vanderbilt.edu/support.html"> -commercial support</A> for ACE+TAO.<P> - <p><hr> <H3>Contributions from the Open-Source Community</H3> <P> |