2007/8/16, Xavier Hanin <[EMAIL PROTECTED]>: > Hi, > > last june I think we agreed on something like that: > 2.0-beta-1: (bug fix + code cleaning + tutorial) late august >
I fear that we are late > 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. > On my site, what I have pending is the end refactoring to isolate the settings per engine. I would also fix the bugs conerning the relative path handling. > 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. > Yes, I think that's required. My problem is that I have little view on what is required in the tutorials. My first guess would be that, the current one must work, and the doc must be updated. But I don't think that's not funny. I have an idea that are I think could be interresting to do: 1. Write an ant script that run every tutorial example and check its result. 2. Put that script into gump 3. Update this script (and the possible the doc)so that the output of each tutorial execution is saved and can be integrated in the doc (maybe with iframe?) Is there anyone who want to contribute? > 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? > I think we are late. We don't have anything to release for the moment, but we should not neither wait too long. What do you think about. - Making the tutorial enhancements, then make a new release of the site - Working on some fix, then make a 2.0-alpha-3 as soon as we have a minimum to release - Make the 2.0-beta1 when we have the major issues fixed (including the maven compatibility). - Then, rather quicly go to beta-2 and 2.0. And concerning the cache managment issue, I have a problem : I don't know what is asked. I have the impression that 12 persons voted for it, but everyone has a different demand. So, before saying that we can put it in 2.0 or not, someone has to sumarize what is asked to see what is the concensus on that. -- Gilles SCOKART
