Hi, My guts feeling is, yes we need that documentation. But we need that release even more. We have been in the incubator for almost 9 month now constantly extending and at least twice rewriting the complete code. It is about time to get a release.
Whether we do a 2.0.0 or a 0.9.0 or an RCx release is minor, actually. We decided a long time ago upon entering the incubator, that Apache Sling's first release will get a major release number and as we already had a private Sling release 1.0 before contributing the project to the ASF, the consequence is to have it like that. In addition, I think, the code itself is pretty stable and warrants a major release number. But this is probably nowhere near a final release, just given the sheer number of open issues we still have and the enhancements requests we expect. So as a starter, I would really go for the release and fix the documentation along the run. Regards Felix Am Freitag, den 30.05.2008, 15:02 +0200 schrieb Bertrand Delacretaz: > On Fri, May 30, 2008 at 2:55 PM, Dominik Süß <[EMAIL PROTECTED]> wrote: > > So why is it defined as major release(just looking at the version number) > > without being a final release?... > > Good point, I agree that 2.0.0 might sound a bit too final for the > current state of the project - the code is fairly solid and > feature-complete, but I agree with you that docs and examples are > lacking. > > I would feel better if the version number was 0.9.0, but considering > that we've been using 2.0.0-SNAPSHOT for ages, I doubt it is possible > to change that at this point, without causing major Maven confusion > (aaarghhh - we don't want Maven confusion do we?). > > What do others think? > > -Bertrand
