Geoff Howard dijo: > > >> -----Original Message----- >> From: Fabricio Chalub [mailto:[EMAIL PROTECTED]] >> Sent: Wednesday, December 11, 2002 2:02 PM >> To: '[EMAIL PROTECTED]' >> Subject: Cocoon 2.1 (was RE: Question about handling of components) > <snip/> > >> Regarding 2.1, I may be wrong, but my impression is that there >> hasn't been a complete overhaul of the entire Cocoon core since >> 2.0, so probably the 'old' 2.0 components are as stable as ever >> in 2.1, while the new features are still a little turbulent and >> thus should be used with caution. >> >> Is this feeling true? Is there anybody here using 2.1.x on >> production servers? How's the stability? > > I think the stability you most need to worry about is stability of the > API - meaning that 2.1 status is currently in flux even as to how things > work and what they are named. If you're going to use 2.1 (as I am on > live projects) you need to at least monitor the dev mailing list for any > discussion on any feature you are using so that you can be forewarned if > the API is changing. You'll also need to be prepared to update from CVS > fairly frequently, which can be a task depending on the complexity of > your project and the > sophistication of your own project's build procedures as relate to > cocoons. > > Geoff Howard
Yes, the complexity of your project will increase, but the reward for using the lastest Cocoon developed technology is priceless! ;-D Antonio Gallardo. > > > --------------------------------------------------------------------- > 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]> --------------------------------------------------------------------- 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]>
