On Apr 15, 2009, at 8:35 AM, Jeff Pierce wrote:
What is the release target for Jetspeed 2.2? I found several posts
from
mid-last year but nothing recent. My project is considering using
J2 as the
underlying technology for its portal-based user interface (shipping
it with
every user interface). The release date is 6+ months out. Would we
be
better off starting with 2.1.3 and moving to 2.2 when it becomes
available
or is the current state of 2.2 stable enough for us to start our
development
against it? There is also the possibility that we could contribute
back to
the project itself if things worked out.
We have slipped quite a bit on the release of 2.2.0. The process of
getting Jetspeed and Pluto synchronized, plus all the new features in
the Portlet 2.0 specification required a lot of refactoring and
implementation work. The team is working towards releasing by end of
April now. We have a small set of issues remaining, I believe its
possible to meet our date. We will also be releasing Pluto 2.0, and
the initial releases of Portals Applications within the same time
period. If you are looking for Portlet 2.0 support, and working with
all the new Jetspeed features coming out this year following 2.2.0, I
would definitely recommend developing against the 2..2.0 release over
the 2.1.x branch. We will maintain the 2.1.x branch for bug fixes. I
hope to have a better roadmap on the site this week. Will send a link
to this list when its there..
Has anyone else shipped Jetspeed as the major component of their user
interface? Or is it primarily used as a development server or
intranet?
yes, absolutely. Speaking just for our company, we are developing
applications that can run in both our CMS product or Jetspeed equally.
We are using Wicket and/or a CMS toolkit for our portlet application
development
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
