On Wed, Jun 27, 2012 at 10:05 AM, Martin Grigorov <[email protected]> wrote: > On Wed, Jun 27, 2012 at 12:06 AM, Martijn Dashorst > <[email protected]> wrote: >> We should just release 6.0. The RC's are the things we create for >> ourselves during the release process. There really is no need IMO to >> push a RC to the mirrors and Maven central for the 10 odd folks >> downloading those. A final release is something people actually care >> about. > > My experience with 1.5 is that the not many users used the milestones > but more started using the RCs and reported issues. > But it will be the same with a final release so I don't really need a RC. > The only difference is that now it wont be possible to do even minor > API breaks as we did in 1.5 RCs, for good or bad.
My experience is that even in 1.5 not many folks were using the RCs. But an RC must not have any api breaks to begin with. If we uncover a bad API (which I am certain exists in Wicket), we fix in Wicket 7 (I hope we are still go for wicket 7? :-). At least from my perspective, we are able to build and run one of our 1000+ page applications using Wicket 6, so I don't think there are any gaping holes in our API. Minor issues, probably. > I can write something about Ajax and Native WebSockets at > http://wicketinaction.com. Great, I'm looking forward to those! Martijn
