The point is not to inform newsplattforms, but the users. While news plattforms only need information about the basic ideas of Sling, the consumers, which will hopefully will be some new developers, need instructions on how to use Sling. I recently checked out apache wicket and they've done a pretty nice work on documentation and examples. You get an idea of how to setup a new project within minutes (sorry but I do not like the "discover-sling-in-15-minutes" Tutorial).
Michael Marth did a good job at his screencasts, but screencasts most times are problembased, not giving the author the possibility to reference other documents or describing complex technical things like resourceresolution. The other problem is - his texts and screencasts are not content of the sling pape where I would anticipate this information. While I do not have the time right now I would really like to define (or at least help to define) a basic but obligatory set of documents for the final 2.0.0 release. Regards, Dominik On Fri, May 30, 2008 at 2:12 PM, Joseph Ottinger <[EMAIL PROTECTED]> wrote: > Of course, now the news platforms - at least one of them - are aware of the > release, but hey. :) > > On Fri, May 30, 2008 at 8:10 AM, Dominik Süß <[EMAIL PROTECTED]> > wrote: > > > 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] > > > > > > > > > > > > > > > > > -- > Joseph B. Ottinger > http://enigmastation.com > Editor, http://www.TheServerSide.com >
