1 / 23

uPortal 2.6

uPortal 2.6. 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. Many deployers of uP 2.x.

Download Presentation

uPortal 2.6

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  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

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

  5. 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

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

  7. About issues

  8. About issues

  9. CVS integration

  10. 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…

  11. Ideas for 2.6 • Stability • Skinning • Layout • …

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

  13. Skinning • Jason Shao’s ideas and efforts

  14. Layout Management • DLM • DLM / ALM marriage • Programmatic creation of fragments

  15. 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.

  16. WSRP consumption

  17. 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

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

  19. 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…

  20. Product Maturity • Stability • Documentation • Administrator tools • Channels duplicating ant task functionality

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

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

More Related