The release I was suggesting that may go out before the holidays would be a bug-fix point release. If we agree to Struts2 and/or Wicket being support modules, they would be new features and I would expect they go in the 1.2 release.
Also, my personal opinion is that I'm firmly against (as a matter of general practice) that we release any new feature without documentation. I would expect there would be new site pages under https://cwiki.apache.org/confluence/display/SHIRO/Integration representing each module and how to use it as well as JavaDoc for every public and protected method/member. Spring, Hibernate, Tomcat, etc. are all successful largely in part because of stellar documentation. IMO, we need to live up to these standards. Regards, Les On Sat, Dec 11, 2010 at 8:39 AM, Alan D. Cabrera <[email protected]> wrote: > I don't see why the struts 2 stuff cannot make it into this release. > > > Regards, > Alan > > On Dec 9, 2010, at 2:27 PM, Les Hazlewood wrote: > >> There are a few issues that have come in the last week that might >> justify a quick point release. I just created a 1.1.x branch to >> account for any bugs we might want to fix in a point release (if we >> actually do one). >> >> With that there, I'm moving the trunk to reflect 1.2-SNAPSHOT so all >> forward-incompatible API changes and enhancements can go in there >> (unless anyone feels otherwise). We just need to know that if we >> apply any patches to the 1.1.x point branch, we should do the same on >> the trunk. >> >> Cheers, >> >> Les
