cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <>
Subject RE: [vote] Starting 2.1-dev
Date Wed, 10 Apr 2002 06:59:59 GMT

Stefano Mazzocchi wrote:
> People,
> I think it's a good thing to plan the future releases now that we have
> created a maintenance branch for the 2.0.x series.
> I propose the following actions:
>  1) set the version of the trunk as 2.1-dev
+1, just checked-in the new version info.

>  2) set the tree processor as the default pipeline manager (means making
> the interpreted sitemap the default one)

I think, it is the default now, right?
We should set the interpreted sitemap as the default in the 2.0.x branch

>  3) merge Schecoon with the main trunk

>  4) remove the compiled sitemap implementation from the trunk [this will
> give more stress on the interpreted sitemap implementation as well as
> removing problems associated with the merging of Schecoon]

>  5) merge the 'sunShine' stuff in the main trunk [one note: I personally
> don't like the use of the term 'sun' so much around there. SunShine,
> Sunlet, SunSpot... I would *strongly* suggest a name change for those
> things, but for sure I like their functionality, even if, in the future,
> they will probably factored out as Cocoon Blocks]
+10 :)

Has anyone a good suggestion for a different name? The base of sunShine is
currently called, well,  "sunShine" - we could merge this with the main
and remove the name there. Then we need only good names for "sunRise",
and "sunLet", I think.

>  6) decide what is solid enough to be moved in the trunk out of the
> scratchpad [NOTE: for 'solid enough' I don't mean 'implementation wise'
> but 'contract wise']



To unsubscribe, e-mail:
For additional commands, email:

View raw message