...

1. Finish merging XWork code base (rename packages)
2. Rename Struts 2 packages to org.apache.struts3
3. Use logging layer from Log4j2 or https://code.google.com/p/anodyzed/ (Chris Pratt is willing to donate that project to Struts)
4. Switch to OGNL 4
   1. we must release it first
   2. 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

M3 (alpha Struts 3)

1. Divide core into api and spi
2. prepare ALPHA release

...

M4 (beta 1 Struts 3)

1. move plugins to separated project
   1. disconnect plugins release cycle from core release

...

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

Undiscussed ideas

• JSR 371 support (https://jcp.org/en/jsr/detail?id=371)
• Better support for modern webframeworks like AngularJS (@grobmeier)
• Make use of slf4j and probably log4j2 (@grobmeier) - support for slf4j is already there, thanks to Johannes, check Logging
• Provide alternatives to java property file translations (@grobmeier)
• Replace css and xhtml theme with an new html5 theme. (@jogep)
• Extract XML configuration to dedicated plugin - XWork will provide only configuration via code, then user can decide which configuration to use - code, XML, convention, DB?
• Should plugins move out of the Struts release cycle so they can independently released? (@pbenedict)
• Turn all request and response processing into interceptors (perhaps introduce a "system stack" to complement a "user stack" to simplify configuration) (@pbenedict)