I think it wouldn't be good for the image of the "product" to release and have news all around in the IT-World without having at least a basic documentation which is up to date. I'd prefer to do a code freeze, build a release candidate and build the documentation within some days.
Then it would be the right time to release and inform all the news plattforms out there about this "milestone in CMS-development" ;). I think it would be good to think of a release like a product. I'd never release a product without a manual. It should not be the goal to fullfill a roadmap concentrating on releasedates, it should be the goal to fullfill all requirements of a release (which IMHO includes documentation). Best regards, Dominik On Fri, May 30, 2008 at 1:58 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > Hi, > > Am Freitag, den 30.05.2008, 13:34 +0200 schrieb Tobias Bocanegra: > > On 5/30/08, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > > > Ten..nine... ...five... ...two...one > > > > > > There's one single issue for a 2.0.0 release in Jira (and it's about > docs), > > > so it really seems that we can release next week. :) > > and this one: https://issues.apache.org/jira/browse/SLING-491 ? > > I just posted a workaround (you certainly know) to the issue. I think > this issue is certainly not a release blocker as it may easily - if so > decided - be added in a maintenance version of the JSP tag lib bundle. > > Regards > Felix > > > > > > > > > So I think it's time to ask if there are any outstanding issues? > Something > > > we are currently not aware of? > > > > > > The final question is, what = which parts we want to release? I think > there > > > are some bundles/modules which we don't need to include in a first cut. > > > > > > WDYT? > > > Carsten > > > -- > > > Carsten Ziegeler > > > [EMAIL PROTECTED] > > > > >
