📄 roadmap.html
字号:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Roadmap - The Apache Struts Web Application Framework</title>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<meta content="Craig R. McClanahan" name="author" />
<meta content="Ted Husted" name="author" />
<meta content="Steve Byrne" name="author" />
<link href="./struts.css" type="text/css" rel="stylesheet" />
</head>
<body>
<div id="heading">
<a href="http://apache.org/">
<img id="asf_logo_wide" alt="The Apache Project" src="./images/asf_logo_wide.gif" />
</a>
<a href="http://struts.apache.org/">
<img id="struts-logo" alt="Struts Framework" src="./images/struts.gif" />
</a>
</div>
<!--end heading-->
<div id="content">
<div id="menu">
<p>Struts</p>
<ul>
<li>
<a href="index.html">Welcome</a>
</li>
<li>
<a href="learning.html">Learning</a>
</li>
<li>
<a href="acquiring.html">Acquiring</a>
</li>
<li>
<a href="using.html">Using</a>
</li>
<li>
<a href="volunteers.html">Who We Are</a>
</li>
<li>
<a href="announce.html">Announcements</a>
</li>
</ul>
<p>Documentation</p>
<ul>
<li>
<a href="userGuide/index.html">User and Developer Guides</a>
</li>
<li>
<a href="userGuide/release-notes.html">Release Notes</a>
</li>
<li>
<a href="api/index.html">Javadoc</a>
</li>
<li>
<a href="faqs/index.html">FAQs and Howtos</a>
</li>
</ul>
<p>Community</p>
<ul>
<li>
<a href="http://jakarta.apache.org/site/bugs.html">Known Issues (Bugzilla)</a>
</li>
<li>
<a href="http://wiki.apache.org/struts">Wiki Pages</a>
</li>
<li>
<a href="http://mail-archives.apache.org/eyebrowse/SummarizeList?listId=241">List Archive</a>
</li>
<li>
<a href="http://wiki.apache.org/struts/StrutsResources">Resource Directory</a>
</li>
</ul>
<p>Download</p>
<ul>
<li>
<a href="http://struts.apache.org/download.cgi">Binaries</a>
</li>
<li>
<a href="http://struts.apache.org/download.cgi">Source Code</a>
</li>
<li>
<a href="http://svn.apache.org/dist/struts/">Development Releases</a>
</li>
</ul>
<p>Development</p>
<ul>
<li>
<a href="bylaws.html">Bylaws</a>
</li>
<li>
<a href="releases.html">Release Guidelines</a>
</li>
<li>
<a href="roadmap.html">Roadmap</a>
</li>
<li>
<a href="http://svn.apache.org/viewcvs.cgi/struts/action/branches/STRUTS_1_2_BRANCH/">Source Repository</a>
</li>
</ul>
</div>
<!--end menu-->
<div id="main">
<h1 id="roadmap">Development Roadmap</h1>
<h2 id="scope">Scope</h2>
<div class="indent">
<p>
This document outlines some of changes we expect to
see in future releases of Struts.
</p>
<p>
This document is provided for discussion purposes only.
All releases and changes to the codebase are subject to
<a href="./bylaws.html">a vote</a> of the
<a href="volunteers.html#pmc">Struts PMC</a>.
</p>
</div>
<h2 id="Bugzilla">Bugzilla Queries</h2>
<div class="indent">
<p>
The Struts development teams uses the <a href="http://jakarta.apache.org/site/bugs.html">Apache Bug Database</a> (Bugzilla)
to manage problem reports and enhancement requests.
For your convenience, here are some common Bugzilla queries:
</p>
<ul>
<li>
<a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Struts&order=bugs.bug_id">Open reports</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=3&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Struts&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Bug+Number">Open reports with at least 3 votes</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=Blocker&bug_severity=Critical&bug_severity=Major&bug_severity=Normal&bug_severity=Minor&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Struts&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=bugs.bug_id">Open problem reports</a>
<ul>
<li>
<a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Struts&bug_severity=Blocker&bug_severity=Critical&bug_severity=Major&order=bugs.bug_id">major problem reports</a>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Struts&bug_severity=Blocker&bug_severity=Normal&bug_severity=Minor&order=bugs.bug_id">normal/minor problem reports</a>
</li>
</ul>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Struts&bug_severity=Enhancement&order=Bug+Number">Open enhancement reports</a>
<ul>
<li>
<a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=Enhancement&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Struts&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=PatchAvailable&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Bug+Number">Patch Available</a>
</li>
</ul>
</li>
<li>
<a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=LATER&resolution=REMIND&product=Struts&order=bugs.bug_id">Reports to be handled "LATER"</a>
</li>
</ul>
</div>
<h2 id="Struts_1_x">Struts 1.x</h2>
<div class="indent">
<p>
Releases in the 1.x series will focus on refactoring of existing functionality, with a
continued emphasis on backward compatibility.
</p>
<p>
New features are being added to the Struts 1.x series,
but only if backward compatability with the prior release can be retained.
The 1.x API is evolving through a deprecate/replace/remove protocol.
Developers are encouraged to stay current with the "best available" release
and to observe deprecation warnings.
Features are deprecated before removal, and deprecated features are ultimately removed.
</p>
<p>
The 1.x series is being refactored into the Struts subproject and several dependant subprojects.
Each subproject is expected to be dependant on the Struts core for necessary functionality.
Otherwise, the subproject should be hosted in another venue, such as Jakarta Commons or Jakarta Taglibs.
</p>
<p>
Popular third-party extensions that are in active use by the Struts Community may be considered
as subprojects, such as those distributed through the
<a href="http://sourceforge.net/projects/struts">Struts SourceForge</a> site.
</p>
<p>
Throughout the 1.x series,
there will be a continued emphasis on expanding unit test coverage for the framework.
Bug reports should include a failing test case when possible.
Proposals for new features should include a working test suite.
(Creating features through Test Driven Development is strongly encouraged.)
</p>
<p>
Enhancement requests are logged in Bugzilla as they are suggested.
<strong>The listing of an enhancement in Bugzilla does not imply that is being "planned"</strong>,
merely that some member of the community has suggested it,
and the idea hasn't been ruled out (yet).
</p>
<p>
Future release milestones are provided for enhancements
which are being actively planned or developed
but may not be ready for the very next release.
If a report has not been tagged for a specific milestone by a working developer,
then <strong>it may never be implemented</strong>.
When developers (including non-Committers) are actually working on an enhancement,
they should re-tag it for a specific release milestone, such as "1.3.1" or "1.3.2".
</p>
<p>
If an enhancement has not been tagged for a specific target,
feel free to start working on it yourself.
Many of our best features have been contributed by developers,
just like you.
If you are working on an enhancement,
post a note on the ticket that you are working on an enhancement
and then post a patch as soon as possible.
If the development effort doesn't succeed,
post a note to the ticket explaining what problem you had creating the enhancement,
so that other developers can explore alternatives.
</p>
</div>
<h2 id="Struts_1_x_whiteboard">Struts 1.x Whiteboard</h2>
<div class="indent">
<p>
These are some general ideas we have about what may happen in the Struts 1.x series.
This is a <strong>whiteboard</strong> and everything here is <strong>subject to change</strong>.
</p>
<ul>
<li>Struts 1.0.0 (complete) -
Major refactoring of Struts internals to provide support for modules and a new "config" object series.
Bundles Struts Tiles and Struts Validator into main distribution.
The initial release of Struts EL is provided as an optional package.
</li>
<li>Struts 1.2.4 (complete) -
Continued refactorings of the Struts 1.x product series.
<ul>
<li>Removed deprecations created in the 1.0 to 1.1 timeframe, and prior</li>
<li>Added support for wildcard mappings.</li>
<li>Other minor enhancements, improvements, and refactorings</li>
</ul>
</li>
<li>Struts 1.2.6 (complete) -
Migrated repository to Subversion; update website.</li>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -