A few comments on various raised points:
> 3) Serious problems (hours lost) upgrading from 2.0 to 2.0.2 - looking
> at the change logs for potential hints at what was necessary was a
> non-starter.
Changes between releases must be documented so that the migration is a
painless as _possible_. But if 2.0 provides what is needed then perhaps
upgrading is not always the best idea. We don't upgrade all our production
installations of Cocoon each time there is a new release. We have Cocoon
based sites that are happily running a pre-2.0 version of Cocoon.
> this will be since there have been significant changes (forms and
> authentication system to just name a few at the feature level) since
> those books have gone to publishing.
>
Unfortunately this is _always_ the case. We finished our book in March (!)
and the printing process is such that it just takes that long before the
book hits the shelves. There is nothing we (as the authors) can do about it
(apart from preventing new Cocoon releases :-)). On the other hand we
decided to include a CD containing a defined version of Cocoon so that the
details in the book match the software. The concepts have not changed
between 2.0 and 2.0.x - but things have been added.
Matthew
--
Open Source Group Cocoon { Consulting, Training, Projects }
=================================================================
Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de
-----------------------------------------------------------------
Cocoon book:
http://www.amazon.com/exec/obidos/ASIN/0735712352/needacake-20
=================================================================
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
