Santiago Gala wrote:
>
> Roberto Rodr�guez Gal�n wrote:
>
> > Rapha�l Luta wrote:
> >
> > > I propose that the work on Jetspeed is organised in the following
> > > fashion.
> > >
> > > * Improve the current 1.2 CVS code in order to release a
> > > clean and working software in the near future.
> > > This involves mostly short term work and will try to preserve
> > > compatibility with the 1.2 beta(s). Maybe we should release
> > > a new beta ASAP so that external people can checkout a code
> > > pretty similar to the one sitting in CVS, this will simplify
> > > user support.
> > >
> >
>
> +1 on having a new BETA. I'm tired of questions regarding bugs that we fixed
> in june or july.
>
+1.
I'd say that such a BETA should go out very quickly (end of next week ?). This
mean the main activity on the HEAD branch should be :
- bug fixing
- documentation update
- installation procedure update
- tests (with various DB/servlet engine)
Feature work would start on the HEAD after the beta is released.
> > This is the most important thing. And it necessary ASAP. Santiago and
> > the rest of people in the spanish group will work hard in this address.
> >
> > > * In parallel to this, start working on a brand new Jetspeed 2
> > > design along with a generic Portlet API.
> > >
> > > * As soon as the Portlet API is solidified, start a back-port of
> > > this API to the 1.2 branch, thus creating a new 1.x Portlet API
> > > implementation.
> >
> > Portlet API is neccesary for all, but it's important to define correctly.
> > >
> > > We have thus a work plan like:
> > >
> > > Short term :
> > > * fix and clean 1.2 branch
> > > => 1.2 release
> > > * start design of new Portlet API
> > > => release a Portlet API
> > >
> > > Mid-term (depends on Portlet API work) :
> > > * start Jetspeed 2 design on top of Cocoon 2
> > > => implement alpha quality implementation
> > > * backport Portlet API to 1.x branch
> > > * identify and componentized shared code between 2.x and 1.x
> > > branches
> > > => release of a 1.x Jetspeed Portal implemented on top of
> > > Turbine
> > >
> > > Long-term :
> > > * release Jetspeed 2 implementation on top of Cocoon 2
> > >
> > > I didn't put any date or timeframe on this since it's a voluntary
> > > contributions ( hint... ;) ).
> > >
> > > I plan to work on the clean up and upgrade of the 1.2 branch and
> > > then focus entirely on the Jetspeed 2 implementation.
> > >
> >
> > The most important think: we will work hard (spanish group) to do JetSpeed
> > 1.2 fine. !
> > "Ask not what JetSpeed can do for you--ask what you can do for JetSpeed."
> >
>
> I'm already working on things like:
>
> - making a list of needed features.
>
> - cleaning remaining multithreading issues and creation of transient objects
> like PortletConfig,...
>
> - isolating daemons, so that:
> - in a simple implementation Jetspeed runs standalone like now
> - in a "farm" implementation, only one Jetspeed (or a database, CMS,...)
> handles external Resources (channels, etc.) and user PSML or stylesheets. The
> other will use HTTP (maybe webDAV, as we need writable resources) to access
> this information. The current implementation in HEAD uses HTTP PUT to save
> resources, but we should have authentification and better webDAV support and
> maybe a simple filemapper for standalone demo or development setup.
>
> - having a look to performance and some "drawing related" bugs in
> controllers/controls
>
Don't devote too much time on this because the system wide use of templates
will probably fix (or change) most issues.
> - solving problems with multi-byte channels. (Example:
> http://www.javable.com/rus/rss.shtml, which currently gets stored in utf-8 in
> the cache, but we loose the russian characters when rendering the portlet. The
> same should happen with japanese or chinese channels, but we don't have any
> yet.) Any help from people that has worked on that issues is welcome. I think
> it is a problem in Xalan or Xerces. It looks a minor problem, but I DO want to
> have a truly global tool for a truly global internet, and I like a lot those
> funny characters that I can't read ;)
>
Great. Could you then coordinate all the bug fixing activity for the next
beta and keep a bug list open ?
--
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]
