With Oracle stopping support for Java 6 this year [1], should we
target Java 7 instead in Wicket 6? Or leave that for Wicket 7?

I'm for keeping Java 6 as our current platform for Wicket 6 (so we
don't add to the confusion with numbering our releases). Wicket 7 can
then be our Java 7 release, and Wicket 8 our Java 8 release :).
Intermitted we can release 6.1 and such in accordance with semver and
provide new functionality in those .y releases.

Martijn, tossing this in front of the wolves :)

[1] https://blogs.oracle.com/henrik/entry/updated_java_6_eol_date

Reply via email to