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

 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]

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

Place your votes.
  

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<[EMAIL PROTECTED]>                             Friedrich Nietzsche
--------------------------------------------------------------------



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to