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.
* 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.
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.
--
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://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
