Author: buildbot
Date: Tue Feb 27 07:56:47 2018
New Revision: 1026036
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/main.pageCache
websites/production/cxf/content/getting-involved.html
websites/production/cxf/content/roadmap.html
Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/getting-involved.html
==============================================================================
--- websites/production/cxf/content/getting-involved.html (original)
+++ websites/production/cxf/content/getting-involved.html Tue Feb 27 07:56:47
2018
@@ -99,7 +99,7 @@ Apache CXF -- Getting Involved
<td height="100%">
<!-- Content -->
<div class="wiki-content">
-<div id="ConfluenceContent"><p>There are many ways you can get involved in
CXF:</p><p>1. Participate on the <a shape="rect"
href="mailing-lists.html">mailing lists</a>. Propose ideas. Comment on others
ideas. <br clear="none"> 2. Look at the open <a shape="rect"
class="external-link" href="http://issues.apache.org/jira/browse/CXF";>JIRA
issues</a><br clear="none"> 3. Provide feedback on the current code<br
clear="none"> 4. Take a look at some of the ideas below</p><h2
id="GettingInvolved-CodingideasforCXFnewcomers">Coding ideas for CXF
newcomers</h2><p>There are many interesting areas of CXF that you could
potentially work on. Some ideas:</p><ul><li>WS-Context & Session
support</li><li>An invoker for <a shape="rect" class="external-link"
href="http://ode.apache.org/";>Ode</a> which uses CXF</li><li>A HTML Form based
"tester" for WebServices</li><li>XMPP/Jabber transport</li><li>Increasing unit
test coverage. Adding unit tests for areas that are not covered by current test
cases is
always valuable to the project.</li><li>Support for Web Service Definition
Language (WSDL) 2.0</li><li>Castor databinding</li><li>Other WS-* support;
e.g., Quality of Service (WS-Atomic Transactions and WS-Coordination),
bootstrapping (WS-MetaDataExchange), WS-BusinessActivity, WS-Eventing and
WS-Transfer</li><li>See the <a shape="rect" href="roadmap.html">Roadmap</a> and
jump in and help</li></ul><h2 id="GettingInvolved-Howtosubmitapullrequest">How
to submit a pull request</h2><ul><li>Open a <a shape="rect"
class="external-link" href="https://issues.apache.org/jira/browse/CXF";>Jira</a>
issue</li><li>Fork the <a shape="rect" class="external-link"
href="https://github.com/apache/cxf"; rel="nofollow">github cxf
mirror</a></li><li>In most cases you should base your changes on the master
branch. The committers can backport to the maintenance branches
then</li><li>Create a new branch named like the JIRA issue you want to edit
(e.g CXF-6738)</li><li>Make your changes, test, and build succ
essfully</li><li>Ideally put all changes into one commit. The commit should
contain the issue id (e.g [CXF-6738] Replace synchronized blocks ...
)</li><li>Push the change to your forked repo into your branch</li><li>If the
commit is named like above it will automatically show up in the JIRA issue
making it easier to see what changes belong to the issue</li><li>If you need to
do changes to your pull request then you should ideally rewrite your commit and
do a push -f to your own branch</li></ul><h2
id="GettingInvolved-Applyingapullrequest">Applying a pull
request</h2><ul><li>Merge the pull request into the branch it is based
on</li><li>Make sure the build works</li><li>Make sure the commits refer to the
issue they solve</li></ul><h2 id="GettingInvolved-Becomingacommitter">Becoming
a committer</h2><ul><li>First off, read about <a shape="rect"
class="external-link"
href="http://www.apache.org/foundation/how-it-works.html";>How the ASF
works</a>. Most importantly, the sections on Meritoc
racy and Roles. That provides a bit of background.</li><li>The important part
is that you need to <strong>earn</strong> the right to be a committer, it's not
something we'll give you just because your name is <a shape="rect"
class="external-link" href="http://en.wikipedia.org/wiki/James_Gosling";
rel="nofollow">James Gosling</a>. To earn the right, you need to get involved.
(see top section above)</li><li>If you become involved, participate in email
discussions, submit patches, etc... the current devs may invite you to become a
committer through a vote. If the vote passes, that will trigger a bunch of
things such as submitting a CLA, creating accounts,
etc....</li></ul><p><em>Hint:</em> submitting pull requests to Jira issues is
the best way. It shows that you are digging into the code, are following best
practices, writing tests, etc.... It also annoys the developers to constantly
have to review patches and if your patches are all acceptable, they'll start
the process to grant commi
ttership just to stop having to review patches. <img class="emoticon
emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png";
data-emoticon-name="smile" alt="(smile)"></p><p> </p></div>
+<div id="ConfluenceContent"><p>There are many ways you can get involved in
CXF:</p><p>1. Participate on the <a shape="rect"
href="mailing-lists.html">mailing lists</a>. Propose ideas. Comment on others
ideas. <br clear="none"> 2. Look at the open <a shape="rect"
class="external-link" href="http://issues.apache.org/jira/browse/CXF";>JIRA
issues</a><br clear="none"> 3. Provide feedback on the current code<br
clear="none"> 4. Take a look at some of the ideas below</p><h2
id="GettingInvolved-CodingideasforCXFnewcomers">Coding ideas for CXF
newcomers</h2><p>There are many interesting areas of CXF that you could
potentially work on. Some ideas:</p><ul><li>WS-Context & Session
support</li><li>An invoker for <a shape="rect" class="external-link"
href="http://ode.apache.org/";>Ode</a> which uses CXF</li><li>A HTML Form based
"tester" for WebServices</li><li>XMPP/Jabber transport</li><li>Increasing unit
test coverage. Adding unit tests for areas that are not covered by current test
cases is
always valuable to the project.</li><li>Support for Web Service Definition
Language (WSDL) 2.0</li><li>Castor databinding</li><li>Other WS-* support;
e.g., Quality of Service (WS-Atomic Transactions and WS-Coordination),
bootstrapping (WS-MetaDataExchange), WS-BusinessActivity, WS-Eventing and
WS-Transfer</li><li>Add visitors for <a shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CXF-5667";>MongoDB</a> and <a
shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CXF-6355";>Solr/
ElasticSearch</a></li><li>See the <a shape="rect"
href="roadmap.html">Roadmap</a> and jump in and help</li></ul><h2
id="GettingInvolved-Howtosubmitapullrequest">How to submit a pull
request</h2><ul><li>Open a <a shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CXF";>Jira</a> issue</li><li>Fork
the <a shape="rect" class="external-link" href="https://github.com/apache/cxf";
rel="nofollow">github cxf mirror</a></li><li>In most ca
ses you should base your changes on the master branch. The committers can
backport to the maintenance branches then</li><li>Create a new branch named
like the JIRA issue you want to edit (e.g CXF-6738)</li><li>Make your changes,
test, and build successfully</li><li>Ideally put all changes into one commit.
The commit should contain the issue id (e.g [CXF-6738] Replace synchronized
blocks ... )</li><li>Push the change to your forked repo into your
branch</li><li>If the commit is named like above it will automatically show up
in the JIRA issue making it easier to see what changes belong to the
issue</li><li>If you need to do changes to your pull request then you should
ideally rewrite your commit and do a push -f to your own branch</li></ul><h2
id="GettingInvolved-Applyingapullrequest">Applying a pull
request</h2><ul><li>Merge the pull request into the branch it is based
on</li><li>Make sure the build works</li><li>Make sure the commits refer to the
issue they solve</li></ul><h2 id="Ge
ttingInvolved-Becomingacommitter">Becoming a committer</h2><ul><li>First off,
read about <a shape="rect" class="external-link"
href="http://www.apache.org/foundation/how-it-works.html";>How the ASF
works</a>. Most importantly, the sections on Meritocracy and Roles. That
provides a bit of background.</li><li>The important part is that you need to
<strong>earn</strong> the right to be a committer, it's not something we'll
give you just because your name is <a shape="rect" class="external-link"
href="http://en.wikipedia.org/wiki/James_Gosling"; rel="nofollow">James
Gosling</a>. To earn the right, you need to get involved. (see top section
above)</li><li>If you become involved, participate in email discussions, submit
patches, etc... the current devs may invite you to become a committer through a
vote. If the vote passes, that will trigger a bunch of things such as
submitting a CLA, creating accounts, etc....</li></ul><p><em>Hint:</em>
submitting pull requests to Jira issues is the best w
ay. It shows that you are digging into the code, are following best practices,
writing tests, etc.... It also annoys the developers to constantly have to
review patches and if your patches are all acceptable, they'll start the
process to grant committership just to stop having to review patches. <img
class="emoticon emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png";
data-emoticon-name="smile" alt="(smile)"></p><p> </p></div>
</div>
<!-- Content -->
</td>
Modified: websites/production/cxf/content/roadmap.html
==============================================================================
--- websites/production/cxf/content/roadmap.html (original)
+++ websites/production/cxf/content/roadmap.html Tue Feb 27 07:56:47 2018
@@ -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><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 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>Support
for additional MicroProfile APIs (e.g. <a shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CXF-7601";>OpenAPI</a>)</li><li><a
shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CXF-6349";>HTTP/2
Transport</a></li><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-CXFversion3.1.x">CXF version 3.1.x</h2><p>The CXF 3.1.x releases
include bug fix releases for issues users encounter with 3.1.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 master 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 3.1.</p><p>See the <a
shape="rect" href="docs/31-migration-guide.html">3.1 Migration Guide</a> for
more details about new features and changes.</p><h2
id="Roadmap-LegacyCXFversions3.0.x,2.7.x,2.6.x,2.5.x,2.4.x,2.3.x,2.2.x,2.1
.x,and2.0.x-EOL">Legacy CXF versions 3.0.x, 2.7.x, 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 3.1.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>
<!-- Content -->
</td>
![https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png"](https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png"){kind=link}