Hi, last june I think we agreed on something like that: 2.0-beta-1: (bug fix + code cleaning + tutorial) late august
We are now at the middle of august, can we try to see if we still plan to release beta 1 before the end of the month, and see which issues we would like to address in this version. IMO, to make it a beta version, we need to work on the tutorials to make sure all of them are up to date and in sync with 2.0 changes. Fixing some more bugs would be nice too. We have already made pretty good progress on code cleaning, a little more wouldn't hurt though. Nothing unfeasible in a couple of weeks, especially if we agree to split the (not funny) work required on the tutorials. The date planned for the first 2.0 RC is approaching too (late september), so maybe it's time to agree on what to include in 2.0. I think we should first focus on bug fixes and documentation update, then on maven 2 compatibility. The flexible cache management has raised some interesting discussions and is still by far the most voted issue (12 votes). Should we try to address it at least partially in 2.0, which could imply postponing the RC cycle? Xavier -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://incubator.apache.org/ivy/ http://www.xoocode.org/
