I promised on the Wicket user list that I would devise a roadmap with some dates on when to expect releases. So here is a preliminary roadmap:
Some dates are not fixed, as there is an approval process to go through before we can ship it: the Apache releases tend to cause a bit more ceremony. When we have graduated you’ll see that these release procedures will become more efficient: there is no extra barrier to pass once we are a top level project. We have started the processes to release both Apache Wicket 1.3.0-incubating-beta and Wicket 1.2.6. The latter will be available this weekend, the former will be submitted to the Apache Incubator PMC for approval. We expect this release to become available around the end of the week after going back and forward a couple of times.
Note the release of wicket-x.y: we don’t know (yet) how to call the version after 1.3. The vote on the development list seems to favor Apache Wicket 2.0. This is a busy weekend for me: building 2 releases. Sounds like a great way to discover if we have improved on the release procedure in the last month.
That’s a really nice picture. What did you use to create it?
I used OmniGraffle to create it.
Pingback: rue’s headroom » Blog Archiv » Wicket 1.3.0 roadmap
I was hoping to learn Wicket in a day this weekend for my upcoming Comparing Java Web Frameworks. I’m guessing I should start with 1.2.6? Are either of these releases available in a Maven repo – or can I checkout/install to get around the lag?
Matt: you can find the pointers to the code here: getting Wicket. 1.2.6 is not packaged yet (you’ll have to do that yourself), but the code in the branches/wicket-1.2.x should not change much.
For learning Wicket I think 1.2.6 is a good place to start.
Hi Martijn! I was looking for information about date of realize of Wicket 1.3. Also I would like to know something more about Wicket 2.0 features and realize date. I am considering writing my bachelor exam on Wicket subject.
Pingback: rue’s headroom » Blog Archiv » Wicket 1.3.0 roadmap
At the risk of asking ac ompletely off-topic question – how did you get that 3-d glassy look on your Omni Graffle doc?