230 likes | 361 Views
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.
E N D
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.
Expected 2.6 release date • Our practice has been to release every six months. • October 2005
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
JIRA • So, let’s identify goals and issues for uP 2.6, schedule them for the release, and work them.
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…
Ideas for 2.6 • Stability • Skinning • Layout • …
Stability, Stability, Stability • Plugging memory leaks • Fixing bugs • Making our portal robust
Skinning • Jason Shao’s ideas and efforts
Layout Management • DLM • DLM / ALM marriage • Programmatic creation of fragments
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.
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
Bugzilla Jira ideas • There are good ideas from our Bugzilla days • Persisting minimizedness of channels as part of layout preferences, e.g.
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…
Product Maturity • Stability • Documentation • Administrator tools • Channels duplicating ant task functionality
Groups and Permissions • Extract out into standalone API / jar deliverable? • (Usable across projects). • Keith Stacks’ Permissions ideas / work • Runtime update to PAGS, e.g.
Other ideas • What enhancements have we made locally? What enhancements do we need?