Re: [ANN] Archetypes Roadmap

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
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
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 :-)

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

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.

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.

> 
> --Paul

Jensens

-- 
Jens W. Klein,               WEB APPLICATIONS: ZOPE, PLONE - MDA, SOA
BlueDynamics Tyrol           production: concept, development, design
Klein & Partner KEG          consulting: analysis, coaching, training
http://www.bluedynamics.com  management: projects, process, community




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