Re: Archetypes.public gone?

On Wed, 14 Jun 2006 18:39:24 +0100, Hanno Schlichting  
<plone-+xqiSR9SqHsk+I/[email protected]> wrote:

> 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.

Okay. Fine. But still, let's apply some practical thinking. Removing  
'public' has no real benefits as far as I can see apart from a minor piece  
of "this is prettier" peace of mind (which I'm not sure I agree with - is  
atapi better than public? does it matter if we have both as aliases?) and  
will unecessarily break a ton of products.

I think we agree on this (I hope anyway) but I think it's important that  
we don't get lost in process and hurt our users because of it.

Martin

-- 
"You can just adapt yourself out of it..." // Archipelago sprint 26/04/2006