Hi, I agree to release a milestone. There are however a few tasks related to the experimental modules remaining before a milestone can be released.
First, wicket-cdi-1.1 needs to be ported from Wicket 6 to 7. The current module in 7 is broken and outdated. I think we can make it part of the core modules in both Wicket 6 and 7. For the other experimental modules, I think we have to look at which modules to keep, which to discard and which to promote. Also, we have to come up with a better versioning scheme, because the 0.x versions clash between 6 and 7. As said before, I think wicket-cdi-1.1 can be promoted to a core module. I'd rather keep wicket-atmosphere experimental. Although the code seems quite stable, I'm not sure if it's because of lack users or because it works fine. We do not use it (yet), because our server stack does not support websockets. Best regards, Emond On Monday 20 January 2014 11:01:36 Martin Grigorov wrote: > Hi, > > With my recent fixes in request mappers code and recovering of page after > expiry I have finished my planned work for Wicket 7. > > Wicket 7.0 > Roadmap<https://cwiki.apache.org/confluence/display/WICKET/Wicket+7.0+ Roadm > ap> is > also covered. > > I suggest that we release a milestone so users willing to help can migrate > their apps and report any issues. > > Here is a JIRA > filter<https://issues.apache.org/jira/issues/?filter=12326080>that shows > all issues which have been fixed/implemented only in Wicket 7.x. I.e. it > excludes issues that are fixed both in 6.x and 7.x. > > At the moment out of 253 issues with FixVersion=7.0.0, 86 issues are 7.0.0 > only. > > We can use this filter to extract "What is new in 7.x" because the > migration guide doesn't show such information. > > > Martin Grigorov > Wicket Training and Consulting
