I'd also like to have a more rapid release schedule. Obviously I'm not
suggesting to keep up with the six-month release train of Java, but we
should provide at least a buildable version for the last LTS version.
That said, like Sven suggested, I'd also like to work on some
improvements before releasing Wicket 9, like WICKET-6563 (new page and
data store architecture) and WICKET-6618 (define a rule to access
stateless pages and components)
On 07/12/18 17:58, Maxim Solodovnik wrote:
IMO there is no need for the 100 breaking changes these days :)
Java11 suppord might be enough
Additionally we can introduce some more fixes in a month or so
No need to wait too long ...
WBR, Maxim
(from mobile, sorry for the typos)
On Fri, Dec 7, 2018, 23:50 Sven Meier <s...@meiers.net wrote:
Hi all,
IMHO Wicket 9.x is in need of some ground-breaking changes - what do we
fill the release announcement with? :P
Btw WICKET-6563 is still waiting for review.
Regards
Sven
Am 07.12.18 um 09:42 schrieb Martin Grigorov:
Hi,
I am fine with this proposal.
Wicket 9 doesn't have many new features compared to 8, so it would be
something like "Wicket 8 for Java 11 users".
On Fri, Dec 7, 2018 at 9:46 AM Maxim Solodovnik <solomax...@gmail.com>
wrote:
Hello All,
I would like to start discussion regarding latest build issues with 6x
and
7x.
My proposal would be: release 9x and make 8x and 9x two main branches
and
7x security fixes branch only.
We were waiting for 8x for too long, so this might be not that bad idea
to
release 9x too early :))
--
WBR
Maxim aka solomax
