Re: Archetypes.public gone?

Andreas Jung wrote:
> 
> I think the general rule in Zope & friends country was to deprecate
> things and remove them after one yr or two major releases..isn't that
> true for Plone or AT?

No. The only documented formal decision we made on this topic is PLIP
115 for Plone http://plone.org/products/plone/roadmap/115, which
effectively states that we have a one release deprecation process.

For example that means an add-on product can either support Plone 2.1
and Plone 2.5 (where you get the deprecation warnings) or Plone 2.5 and
Plone 3.0 after you fixed all code to not show deprecation warnings for 2.5.

We do use the 'no deprecation after a .0 release' rule though. That
means the potentially last moment we might add a deprecation for
something is right before a .0 final release is made.

A true one-year deprecation time has been impracticable so far as that
would have meant for example for Plone 3.0 to be Zope 2.7 (without Five)
compatible up to eventually Zope 2.11, as Plone 2.1 (the release made
one year before Plone 3.0) supported it. Most of the deprecation
warnings we fix results from changed API's coming from lower layers of
our stack.

The other main part where we deprecate things are on the UI level in
form of Python scripts or tools API. Carrying these around for more then
one release has been considered to be too much of a burden without a
major benefit.

After all one should not forget that Plone and the packages it consists
of are a product and not a framework ;) We usually support the current
and next version both on the level of API's as well as in form of
bug-fix releases. We don't have the resources to support an older version.

Hanno