cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <>
Subject Re: [vote] Starting 2.1-dev
Date Wed, 10 Apr 2002 13:20:45 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


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


>  3) merge Schecoon with the main trunk

I'm with Ovideau on this--and he is the author.  I like the idea, but it
needs to be polished a little more first.  I am looking forward to
seeing how it works in the future.

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

+1  That thing has been a thorn in my side.

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

+1, and I aggree with your statement.  Sun would file trademark
infringement lawsuits on the great big ball of fire in the sky
if they could.

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


>  7) ???

Start work on the component model....


"They that give up essential liberty to obtain a little temporary safety
  deserve neither liberty nor safety."
                 - Benjamin Franklin

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

View raw message