1. uPortal 2.6

2. Yes, there will be a uPortal 2.6 Many institutions using uPortal 2.x Have needs for new features, bugfixes, and improvements Will be using uPortal 2.5 And will be looking forward to additional features, bugfixes, and improvements in a uP 2.6.

3. Many deployers of uP 2.x

5. Expected 2.6 release date Our practice has been to release every six months. October 2005

6. JIRA Tool allows us to: –Identify issues (report issues) –Schedule them for a release –Take responsibility for them (assignment) –Comment about the issues –Mark them completed –See progress towards a release

7. JIRA So, let’s identify goals and issues for uP 2.6, schedule them for the release, and work them.

8. About issues

10. CVS integration

11. The Head is an exciting place to be ALM / DLM work Improved JSR-168 support Spring and PersonDirectory Chaining Throwables (thanks, Eric) Bugfixes JAXP 1.3 And more…

12. Ideas for 2.6 Stability Skinning Layout …

13. Stability, Stability, Stability Plugging memory leaks Fixing bugs Making our portal robust

14. Skinning Jason Shao’s ideas and efforts

15. Layout Management DLM DLM / ALM marriage Programmatic creation of fragments

16. Nested tabs As more content becomes available –e.g., Sakai as veritable treasure trove of content As layout fragments can be created programmatically at runtime We need more real estate in which to present the components.

17. WSRP consumption

18. Sakai integration work Improving uPortal by taking advantage of resources made available by Sakai –Skinning, layout management, nested tabs, WSRP consumption –Also enabling more portlet view technologies

19. Bugzilla  Jira ideas There are good ideas from our Bugzilla days –Persisting minimizedness of channels as part of layout preferences, e.g.

20. Issues that slipped the 2.5 release Lots of issues for 2.5 we’re not going to get to before the 2.5 release…

21. Product Maturity Stability Documentation Administrator tools –Channels duplicating ant task functionality

22. Groups and Permissions Extract out into standalone API / jar deliverable? –(Usable across projects). –Keith Stacks’ Permissions ideas / work Runtime update to PAGS, e.g.

23. Other ideas What enhancements have we made locally? What enhancements do we need?