JetSpeed 2.0/1.6 Timelines (JSR 168)

["Mike R." <ra...@rogers.com>]

Hello -

We are developing a portal prototype to be used in a demo for the 
Canadian gov (GoC).  A significant requirement is JSR 168 compliance.
Our demo is targetted for completion in 3-4 weeks.
Requirements summary is:

- 4-5 portlets
- rendering via JSPs and XSLT
- no frames, no min/max/help/edit buttons; maybe even no title bar
- use of PortletSession to track user navigation (breadcrumbs)
- possibly some minimal inter-portlet communication (TBD)
- must be stable enough to be used in a demo
- tight schedule, so I don't want to be upgrading to Jetspeed fixes on
a regular basis.


Our initial thinking was to use Jetspeed 2.0. Having looked briefly at 
J2, I am concerned that its "alpha version" characteristics (robustness, 
bug list, lack of "how to" doc, design changes, etc.) is a risk factor.

My current understanding is that 1.6 is being retrofitted for JSR168 
support (read a post by Raphaël Luta to that effect). So the questions are:

1.  Is 2.0 stable enough for our requirements?  (The JIRA stats look 
sort of scary)
2.  What is the projected stable release date for a JSR 168 compliant 1.6?
3.  What is the next projected release date/version for 2.0?
4.  Will 2.0 have better "How To" documentation soon?

Note: I would really appreciate David Sean's input to this question.

Thanks.

Mike R.
Application Architect
AAFC (GoC)



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

Re: JetSpeed 2.0/1.6 Timelines (JSR 168)

[David Sean Taylor <da...@bluesunrise.com>]

Mike R. wrote:
> Hello -
> 
> We are developing a portal prototype to be used in a demo for the 
> Canadian gov (GoC).  A significant requirement is JSR 168 compliance.
> Our demo is targetted for completion in 3-4 weeks.
> Requirements summary is:
> 
> - 4-5 portlets
> - rendering via JSPs and XSLT
> - no frames, no min/max/help/edit buttons; maybe even no title bar
> - use of PortletSession to track user navigation (breadcrumbs)
> - possibly some minimal inter-portlet communication (TBD)
> - must be stable enough to be used in a demo
> - tight schedule, so I don't want to be upgrading to Jetspeed fixes on
> a regular basis.
> 
> 
> Our initial thinking was to use Jetspeed 2.0. Having looked briefly at 
> J2, I am concerned that its "alpha version" characteristics (robustness, 
> bug list, lack of "how to" doc, design changes, etc.) is a risk factor.
> 
> My current understanding is that 1.6 is being retrofitted for JSR168 
> support (read a post by Raphaël Luta to that effect). So the questions are:
> 
> 1.  Is 2.0 stable enough for our requirements?  (The JIRA stats look 
> sort of scary)

My opinion is that 2.0 is stable enough for your needs.
The deployment state is probably the biggest problem.
Ate's refactoring will solve the deployment issues.
I've reviewed his work: its top notch (like everything he does).
And if you don't need live deployment, its not an issue.

> 2.  What is the projected stable release date for a JSR 168 compliant 1.6?

I seem to be the bottleneck there. Its been delayed for several months 
now. Im nearing completion of a project this month that has been 
consuming all of my time. I should be freeing up soon. Planning for 1.6 
to go out before the end of the month or first week in April.

> 3.  What is the next projected release date/version for 2.0?

May

> 4.  Will 2.0 have better "How To" documentation soon?
>
For the final release it is required.

I can setup a demo of Jetspeed-2 running for you if you'd like.
Contact me personally. I'd make it public, but Im tired of setting up 
demos publicly, and then having  people change the passwords within 
hours of the announcement.

-- 
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org