Ate Douma wrote > > The above list in my view now covers most if not all critical *design* > issues for Pluto container SPI and implementation. > Once we have "fixed" the above, I think the Pluto container will finally > be stabilized out enough as basis for an actual 2.0 release. > Sure enough, there also will be implementation bugs to deal with, but > those should (hopefully) no longer require major SPI and implementation > refactoring. > > Besides David and myself, I hope also some other Portals committers and > community members will be able to help out with this on short notice > because our goal is to get this "done" before the upcoming ApacheCon, > end of march in Amsterdam. > > I'm looking forward to feedback and discussion of the above, > Hi,
thanks for this list, Ate! Now, I haven't looked at the code yet and I'm not that familiar with Pluto 1.1 either, but reading through your proposal I think it sounds right to do these changes, so +1. I'm not sure if I can help out, but I'll start integrating Pluto into Sling next week :) Carsten -- Carsten Ziegeler [email protected]
