The idea that Plone is going to stop using Archteypes seems to be percolating out there in the wild somewhere. As Martin definitively states: it’s not true.
Hi all,
Just in the interest of avoiding confusion and doubt:
The Plone team have no immediate plans to remove Archetypes or stop maintaining it
Archetypes is alive and well. It has a new, pragmatic and
reliable maintainer in Daniel Nouri. We all use it. Our customer
deployments all rely on it. New documentation is being written for it.
Plone’s core content types are all built with Archetypes. Probably 90%
of third party components are built on it as well.It is true that there are new technologies that overlap in
part with what Archetypes has covered in the past, such as better ways
of making references between content or new ways of generating forms
(especially when those forms are not meant to edit a content object).
As Archetypes evolves, we will standardise on more such technologies
and improve Archetypes’ ability to interoperate with other parts of our
stack. This is the way our evolution has always happened.That does NOT mean that all your AT-based content types will
suddenly stop working. So long as you keep testing your code with the
version of Plone you want it to run with, and listen to deprecation
warnings to pre-empt things being removed (after the standard
two-version deprecation period) all will be well.In Plone 3, Archetypes has gained a few new features that make
Archetypes content types a bit more fleixble. To my knowledge, “plain”
Archetypes content types should not break in Plone 3.In other words – this is a big message about nothing. But just
like the “Plone 3 will run on pure Zope 3″ myth (also not true!) this
one is dangerous if a number of people believe it to be true.Regards
Martin
The Plone Blog: March Martin Mythbusting
Originally from Planet Plone by