Raphael Luta wrote:
> I'd like that all committers vote on the following points
> in order to better define what needs to be done in the
> clean-up/bugfix process for 1.2:
>
> Point 1: Project module
> In the CVS, in /modules/project sits a project management
> code contributed by Sandy Metzger and apparently left alone.
> This code is neither compatible with the Jetspeed engine,
> nor Turbine and has not been picked up by anybody after
> we moved it out of the engine in April/May.
>
> I'm +1 to remove it from the repository unless someone
> steps up right now to take over it.
>
+1. I did not even noticed that it was there.
>
> Point 2: Cocoon support
> In my TODO list for 1.2, I mentioned that the Cocoon
> support was a hack and was going to fail with Cocoon 1.8.
>
> I proposed to remove completely its use from the engine
> (thus affecting MemoryStore and a few basic functionalities
> like PortletBrowser, etc...). I think CocoonPortlet should
> be kept but as a Portlet example, not something we rely on.
>
> I'm +1 on this.
>
I would say -1 until after this weekend. I'll be working on
Cocoon-Jetspeed integration issues with Ricardo Roche during the weekend
in Madrid, and I would like to have this point freezed until I discuss
the integration with him. After the discussion, we can have clearer
ideas.
I would like to know what are the hot issues with respect to integration
with Cocoon 1.8, as he told me that he believed that adding proper
support for Cocoon looked like a simple work. It may be that we have
proper 1.8 support after the weekend.
More informed opinions? If the issues justify it, I could be convinced
before the week end. But I think having Ricardo working with us could
solve a lot of issues. It is important, though, that we post our
conclusions so that we can have a public discussion on the Cocoon
support.
>
> Point 3: Castor support
> Again from my TODO list: should we stick to Castor for 1.2 ?
> The alternative is to recreate all these API using a Peer
> model for example.
>
> I'm -0 for this: I'd like to remove it but I don't think
> we have enough resources for this for 1.2.
>
Like other people, I think that a fast release should imply that we
concentrate resources on other tasks. I don't understand the code there,
so I'm -0.
>
> --
> Rapha�l Luta - [EMAIL PROTECTED]
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
