================================================================================
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
================================================================================

                      Release Plan for Apache Tomcat OACC
                      ===================================


Introduction:
------------

This document is a release plan for the development of Apache Tomcat OACC.

The goal of the Apache Tomcat OACC is to provide a port of Tomcat 5.5 cluster
to Tomcat 6.

The default cluster contained in Tomcat 6 is more powerful than the previous
Tomcat 5.5 cluster. To achieve this goal, the implementation has changed
completely and the configuration is very different from the previous one.

Users with HA (high-availability) requirements usually have a very conservative
position with respect to big changes of the infrastructure. In order to allow for
an easier migration path from Tomcat 5.5 to Tomcat 6, OACC allows to use the
original Tomcat 5.5 cluster configuration and implementation inside Tomcat 6.

Users can therefore first migrate to Tomcat 6 using the cluster module they
have gotten familiar with, and in a second step they can switch over to the
default Tomcat 6 cluster implementation.

Stability
---------

Apart from porting issues, OACC will soon be called stable, because the OACC code
is nearly identical with the stable Tomcat 5.5 cluster module.

The project will try to keep Tomcat 5.5 cluster in sync with OACC.

There are no plans for major changes to OACC.