I had a lot of request recently whether to wait for Wicket 6 instead of
migrating to 1.5.x.
Seems there are a lot of projects still running on 1.4.x, so I'm all in
favor of a milestone soon.
Hopefully this will bring people to speed with their upgrade plans.
Sven
On 03/20/2012 09:39 AM, Emond Papegaaij wrote:
I totally agree. Wicket 6 is almost feature complete, and it's time for a
bigger audience to test it. I also agree on the second part: RCs should not
have API changes, and if they do, they should be very small and contained to
parts of the API that already changed between 1.5 and 6.
Emond
On Monday 19 March 2012 11:49:12 Martin Grigorov wrote:
Hi,
What do you think about a release of 6.0 as a milestone this week ?
Looking at Jira I see only CDI integration as something bigger but
afaik it wont bring any API breaks, it will just add a new
module/functionality.
I'm also helping Andreas Pieber in providing better integration for
OSGi. Hopefully this wont require API breaks.
I'd like to release a milestone or two before the release candidates
because we wont be able to fix or improve the APIs in the RCs.
We had a few API changes in 1.5 RCs and this made some users more or
less not happy. Let's try to avoid this this time.
I also would like to ask Wicket devs to spend some time and review the
new stuff (code, migration page, docs) if they didn't so far. Their
feedback is most valuable!
