svn commit: r1012286 - in /websites/production/cxf/content: cache/main.pageCache roadmap.html

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

svn commit: r1012286 - in /websites/production/cxf/content: cache/main.pageCache roadmap.html

buildbot
Author: buildbot
Date: Mon May 15 21:48:19 2017
New Revision: 1012286

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/main.pageCache
    websites/production/cxf/content/roadmap.html

Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/roadmap.html
==============================================================================
--- websites/production/cxf/content/roadmap.html (original)
+++ websites/production/cxf/content/roadmap.html Mon May 15 21:48:19 2017
@@ -99,7 +99,7 @@ Apache CXF -- Roadmap
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><h1 id="Roadmap-Roadmap">Roadmap</h1><p>Current Roadmap for future versions of CXF. (This is an ongoing "work in progress", subject to change.) Note that a primary goal of the Apache CXF team is to make frequent CXF releases. This includes major, stabilized, and thoroughly tested releases, as well as minor patch releases.</p><h2 id="Roadmap-Futureversion">Future version</h2><p>These may find their way into one of the releases below if people step up to finish them.</p><ul><li>SOAP/TCP support (GSoC project)</li><li>Better management capabilities</li><li>Better Acegi integration</li><li>Update to WS-RM 1.1</li><li>Enhancements to WS-Trust support</li></ul><h2 id="Roadmap-CXFversion2.7.x">CXF version 2.7.x</h2><p>The CXF 2.7.x releases include bug fix releases for issues users encounter with 2.7.x versions. These releases will be done on a branch by selectively merging fixes from the trunk on an as-needed basis. For the most part, there would be fixes for:<
 /p><ul><li>Interopability issues</li><li>Critical show stoppers</li></ul><p>Some new features may be back ported from trunk to provide some new functionality to users quicker if it doesn't affect the existing stuff or can enhance some of the new features in 2.7.</p><p>See the <a shape="rect" href="http://cxf.apache.org/docs/27-migration-guide.html">2.7 Migration Guide</a> for more details about new features and changes.</p><h2 id="Roadmap-LegacyCXFversions2.6.x,2.5.x,2.4.x,2.3.x,2.2.x,2.1.x,and2.0.x-EOL">Legacy CXF versions 2.6.x, 2.5.x, 2.4.x, 2.3.x, 2.2.x, 2.1.x, and 2.0.x - EOL</h2><p>Versions of CXF prior to 2.7.x are no longer supported at Apache. They are now considered end-of-life and are therefore unsupported. Users are highly encouraged to <a shape="rect" href="http://cxf.apache.org/docs/migration-guides.html">migrate</a> to newer versions of CXF.</p></div>
+<div id="ConfluenceContent"><h1 id="Roadmap-Roadmap">Roadmap</h1><p>Current Roadmap for future versions of CXF. (This is an ongoing "work in progress", subject to change.) Note that a primary goal of the Apache CXF team is to make frequent CXF releases. This includes major, stabilized, and thoroughly tested releases, as well as minor patch releases.</p><h2 id="Roadmap-Futureversion">Future version</h2><p>These may find their way into one of the releases below if people step up to finish them.</p><ul><li>SOAP/TCP support (GSoC project)</li><li>Better management capabilities</li><li>Better Acegi integration</li><li>Update to WS-RM 1.1</li><li>Enhancements to WS-Trust support</li></ul><p>You should also check the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CXF/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel">JIRA Road Map</a> for the latest information.</p><h2 id="Roadmap-CXFversion2.7.x">CXF version 2.7.x</h2><p>The CXF 2.7.x re
 leases include bug fix releases for issues users encounter with 2.7.x versions. These releases will be done on a branch by selectively merging fixes from the trunk on an as-needed basis. For the most part, there would be fixes for:</p><ul><li>Interopability issues</li><li>Critical show stoppers</li></ul><p>Some new features may be back ported from trunk to provide some new functionality to users quicker if it doesn't affect the existing stuff or can enhance some of the new features in 2.7.</p><p>See the <a shape="rect" href="http://cxf.apache.org/docs/27-migration-guide.html">2.7 Migration Guide</a> for more details about new features and changes.</p><h2 id="Roadmap-LegacyCXFversions2.6.x,2.5.x,2.4.x,2.3.x,2.2.x,2.1.x,and2.0.x-EOL">Legacy CXF versions 2.6.x, 2.5.x, 2.4.x, 2.3.x, 2.2.x, 2.1.x, and 2.0.x - EOL</h2><p>Versions of CXF prior to 2.7.x are no longer supported at Apache. They are now considered end-of-life and are therefore unsupported. Users are highly encouraged to <a sha
 pe="rect" href="http://cxf.apache.org/docs/migration-guides.html">migrate</a> to newer versions of CXF.</p></div>
            </div>
            <!-- Content -->
          </td>