| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> |
| <html> |
| <head> |
| <META http-equiv="Content-Type" content="text/html; charset=UTF-8"> |
| <title>Release Plan</title> |
| <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"> |
| <meta content="Planning Documentation" name="DC.Subject"> |
| <meta content="The Cocoon Community" name="DC.Creator"> |
| </head> |
| <body> |
| |
| <h1>Timeframe</h1> |
| |
| <p>This is the current time frame for the next releases:</p> |
| |
| <ul> |
| |
| <li>Not schedulded yet: 2.1.7 (maintenance release)</li> |
| |
| <li>Not schedulded yet: 2.2M1 (Milestone 1)</li> |
| |
| </ul> |
| |
| |
| |
| <h1>Roadmap</h1> |
| |
| <p> |
| In general, the next Cocoon version 2.2 can be seen as the |
| "consolidation version". In the past a lot of new features, blocks |
| and components were added which resulted in the fact that |
| in some places concurring solutions were developed that could be |
| combined a little bit. |
| </p> |
| |
| <p> |
| One good example is form handling where we now are concentrating |
| on CForms. We will try this in other areas as well. Of course this |
| does not mean that we won't add new features to 2.2, but we try to |
| consolidate what we currently have as well. |
| </p> |
| |
| <p> |
| The follow is a list of items that are planned for the next minor release |
| of Cocoon (2.2). This is a dynamic list that might change over time :) |
| </p> |
| |
| <p> |
| We have come to the conclusion that real blocks might take a little bit |
| longer than we have expected. So we agreed on not affecting the current |
| development of Cocoon by the real blocks development. Which means we have |
| to develop the blocks system separately from Cocoon until the block |
| system is stable enough to be "merged" into Cocoon. This allows us to |
| release new versions of Cocoon (like 2.2) without waiting for blocks to |
| be working/finished. |
| </p> |
| |
| <ul> |
| |
| <li>Official Versioning Guide (will be published soon).</li> |
| |
| <li>Virtual Sitemap Components.</li> |
| |
| <li>First finished version of CForms.</li> |
| |
| <li>Deprecate (not remove!) XSP (and provide a viable alternative).</li> |
| |
| <li>Cleaning up the caching/store mess.</li> |
| |
| <li>Deprecate blocks that haven't been maintained in a long while |
| or don't serve any evident purpose. Web3, Apples, Python, |
| Asciiart might be some candidates. We will decide this on a |
| case-by-case basis. |
| </li> |
| |
| <li>Differentiate between blocks that provide a service to other |
| blocks and blocks that contain just samples or small applications |
| built upon cocoon (petstore, tour, linotpye). Maybe "samples-only" |
| blocks should be a separate download. Perhaps remove deprecated blocks etc. |
| </li> |
| |
| <li> |
| Review the implications and the implementation of pooling. |
| </li> |
| |
| <li> |
| Reduce unneeded dependencies on Avalon, where possible. |
| </li> |
| |
| <li> |
| Review the logging framework. Log4j is the de-facto standard and |
| we have blocks that complain if Log4j is not properly configured, |
| so let's accept it and stop reinventing the wheel. |
| </li> |
| |
| <li> |
| Write more tests (you knew this one was coming ;-) ). |
| </li> |
| |
| </ul> |
| |
| <p> |
| The <a href="updating.html">updating to 2.2</a> document contains |
| more information on how to prepare your application for the next minor |
| release. |
| </p> |
| |
| |
| |
| <h1>The Future</h1> |
| |
| <p> |
| We already have plans for further versions of Cocoon that might be |
| long in the future... |
| </p> |
| |
| <ul> |
| |
| <li>Design and implement blocks.</li> |
| |
| <li>Integrate Kernel into the Cocoon core.</li> |
| |
| </ul> |
| |
| |
| |
| </body> |
| </html> |
