First of all, if you see my second mail that I fired few minutes before... you will realize one of the ideas behind going for a 2.0. Since the XML Schema compliance will make some changes to the configuration language. Yes Ruwan, this definitely explains a move to 2.0. I just noticed your mail shortly after sending out my first one.
We can do a 1.3 from the branch, but we cannot just dump the release, we need to complete documentation, do testing and so forth, which will result in more work. Having the above said features on the trunk and the schema compliance sort of changes planned to go into the trunk. I don't like to waste time on those aspects on 1.3 branch. Of course this is an argument. I am about to send a release plan, it will at least take another month for the 2.0 release, but will be much more effective the time than spending another 2 weeks and doing a 1.3 release, with lesser features than trunk. Ok, I think it makes sense to wait for the plan before sharing further thoughts. ;-) Being said all that, if the user community is really interested in the 1.3 we could of course go for it before 2.0. I’m not sure, but I would guess the community doesn’t care too much about version numbering. Most users might be interested most in getting bug fixes and features which are at the moment only available on trunk – e.g. working REST-support – as soon as possible. On the other hand especially new users might be more than happy to wait a few additional weeks to start directly with schema-aware configuration which is definitely a feature which has been requested a lot in the past. Regards, Eric
