Switch to strict DMI by default - allow only defined methods to be accessible via DMI - user can always change that list

prepare second beta

drop support for "top" object - this can be painful, users are using so migration path is needed

Cleanup website

new user guide totally developed out of Confluence - people will be able to contribute to it via GitHub

Confluence (wiki) used only to explain more detailed given aspect of the framework (ie.: how to implement your own converter in details)

keep just one version of the doc (no more release/2.3.x, release/2.2.x and so on - Google indexes everything and people are confused)

prepare the last beta

M2 (aka Struts 2.6)

Servlets 2.5, JSP 2.1, Java 7

struts-api module

Drop support for internal logging layer and use Log4j2 only

M3 (beta 1 Struts 3)

Servlets 3.0, JSP 2.2, Java 8

Finish merging XWork code base (rename packages)

Rename Struts 2 packages to org.apache.struts3

Switch to OGNL 4

we must release it first

also we need better API interfaces to allow integrate Struts with other EL engines, ie.: MVEL - right now the whole conversion layer is hardly tied with OGNL

Switch to Servlet Specification 3.0

drop embedded JSP plugin

M4 (beta 2 Struts 3)

move plugins to separated project (need to be discussed)

disconnect plugins release cycle from core release

Cleanup website

There should be just one project website - Apache Struts. Right now there is the main website - Apache Struts project, subsite Apache Struts 1 and another subsite Apache Struts 2. After announcing EOL of Struts 1, we basically supporting just one version or rather branch - Apache Struts 2 which should be at some point converted just into Apache Struts (version 2.5, version 3.0, version 3.1, etc.).

With that in mind we should have just one website to manage the project.