Basically +1 to target jdk 1.6 for wicket 6; but not because of the
version number but because it will take ages for ppl to adapt to java 7
(independently if oracle supports it or not). Secondly I'm not so sure
about binding the major releases to the jdk versions. If semantic
versioning is still honored and there is no contract break except in the
major releases I think it's basically OK, BUT what if it takes oracle
e.g. 3 years to release java 8? do we really want to wait that long to
introduce API breaks?
Kind regards,
Andreas
On 02/16/2012 05:06 PM, Martijn Dashorst wrote:
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
