i am already busy and i think almost done with: second level caching stateless pages/components delayed session
I just have to figure out if i don't forget anything.. johan On 11/8/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> I think that is a solid idea, but I also want the 1.x branch to follow > 2.x as closely as possible feature wise. This is also nice for those > reading the book that things still work as explained in 1.x. > > Not everything, but having a similar hierarchy for models would help. > Having validators work in similar fashion would help too. Here is where we disagree though. I'm not for keeping 1.x close to 2.0 at all. We planned on letting 1.3 be the branch close to 1.2, but with a couple of fixes and enhancements we couldn't do in 1.2 due to binary compatibility. A similar hierarchy for models and validators that work in the same way are in my book not important enough to justify the time we distract from working on 2.0 and for more API breaks. But that's just my opinion. If it's on the top of your list, well, this thread is where you can state that then. I am just hoping that 1.3 stays close to 1.2 now (I'm sure the readers of Pro Wicket can appreciate that as well), and that we can put 1.3. in maintenance state very soon too. Eelco
