Re: [ANN] Archetypes Roadmap

Jens W. Klein wrote:
> Am Thu, 02 Feb 2006 09:14:53 +0100 schrieb Paul Everitt:
> 
>> Jens W. Klein wrote:
>>> Hi and greetings from the 3rd SnowSprint in Egg/Austria,
>>>
>>> we decided today the Roadmap for Archetypes:
>>>
>>> 1) the 1.3 series will end with it's next release 1.3.8-final (except if
>>>    there are real serious bugs found). Its production ready and theres
>>>    need to pollute it with new features anymore.
>>>
>>> 2) Archetypes 1.4 is the official release for Plone 2.5 and will work for
>>>    Plone 2.1.2 and 2.5.x on Zope 2.8.5+. It's changes are minor.
>>>    Integration of generator, separated UIDCatalog from ReferenceEngine
>>>    almost w/o touching the implementation and deployment with additional
>>>    Product Marshall. We will also get image transformations into
>>>    PortalTransforms!
>> By Marshall, do you mean the Marshall product in the Collective?
> 
> Yes. We need this cool piece of software to make easy generic import and
> export of content possible. 
> For example we're developing at the moment
> XMLForest https://svn.biblhertz.it/repos/public/XMLForest/trunk/XMLForest

Ahh, hadn't seen that.

> which also will make migration/deployment of Archetypes based content very
> easy. I know Kapil is working on something similar. There've been
> coordination between Kapil, Phil and Gogo in past. 
> The current problem with Marshall at the moment is just that theres

Well, that changed recently. :^)  Sidnei and I made not one, but two 
releases:

   http://plone.org/products/marshall

Also, since I've whined about lack of docs on XML stuff, I spent some 
time documenting Marshall (mostly so I'd know how to use it again):

   http://plone.org/documentation/tutorial/xml-in-plone-with-marshall

I plan to add to that tutorial with an explanation of CTRExtras and the 
use of <cmf:type> to avoid mangling file extensions.

> currently no real release management. Anyway, we need to improve it. There
> are two options: Enfold does release management or I'll step into this. It
> includes QA, merging important branches (or coordination of how we could
> make features in branches own Products), tagging and publishing at
> plone.org in sync with Archetypes Roadmap. Hey, if someone (Sidnei, Alan)
> is reading it, please give me a statement :-)

I've started experimenting with a refactoring of handlers/_xml.py, with 
the goal of having it use lxml instead of libxml2 and minidom.  I'm also 
interested in ways to improve the fidelity and "meaning" that is packed 
up into the serialization.

I'm also interested in making the XML model and the AT model more 
semantically related by using the namespace extension stuff in lxml:

   http://codespeak.net/svn/lxml/branch/scoder2/doc/namespace_extensions.txt

The idea is that you could have an AT instance whose state was expressed 
as an Element Tree, and you'd use the same methods as AT to operate on 
it.  I have no idea yet how far this will go before it fails.

>>> 3) Archetypes 1.5 goes Zope 3. It will depend on Zope 2.9 and Plone 2.5.
>>>    Implementation of Archetypes PLIP 5 'Componentize Reference Engine' is
>>>    already in a good shape. If its finished the first alpha will be
>>>    released.
>> Archetypes 1.5 will still be backwards compatible with existing tests, 
>> schemas, and pickles, correct?
> 
> Archetypes 1.5 will be backwards compatible with all above. But the API
> will change. We'll deprecate old API to enforce usage of the component
> architecture.

Ok, that's fine.  You'll do deprecation the normal way, where it warns 
for a Plone release, then breaks in a later Plone release?

> For the UID/ReferenceEngine we will have two steps: In 1.5 the old style
> ReferenceEngine will be implemented using component Architecture. Whit,
> Alec, Frisi, Daniel and I are working on it. It is 100% componentized, you
> can configure it to use RFC4122 compliant UUID's, but default is old
> Archetypes logic. You can configure it to use Zope3-Annotations, but
> default is old Archetypes UUID_ATTR, etc.

I think this is a great step.  But I'm a moron, so this is hardly a 
ringing endorsement. :^)

> In 1.6 we will have a refactoring of the way references are handled
> itself: make it more Pythonic. The components are planned to be fully
> independent UID-/Reference-Engines, which make them available for
> the whole Zope Community. You can choose to use the old style code, but
> we'll start deprecating all code that depends on Archetypes the
> Zope2-Product. And here we will have migration code (we're planning to use
> zope 3 generations for those migrations).
> 
> We go the same road for all other parts: 
> 
>              A smooth and cosy componentization path.
> 
> I hope now our plans are better explained.

Yep, thanks!

--Paul



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642