...
When we imported our Bugzilla instance into our modern issue tracking system, JIRA, we imported a number of issues that are still applicable. We should review these and determine which, if any, should be scheduled to be addressed on the uP 2.6 timeframe.
Issues that slipped the 2.5 release
Some issues will slip the 2.5 release. For some issues, this is because they weren't actually important enough to be addressed. For others, we've just run out of time on good ideas and they should be scheduled for the 2.6 timeframe.
product maturity
Beyond stability, there are ways in which uPortal can become a more mature product. This includes administrative tools. To what extent is smoothing administration something upon which we wish to focus for uPortal 2.6?
Groups and permissions
uP 3 will be looking to use the uP 2 groups and permissions functionality. This will be an opportunity for both products to take advantage of a spun out groups and permissions API – as well as to make this API available for other projects.
Also, Kieth Stacks of SunGard SCT will be working on a "finer grained permissions" effort which we can expect to have deliverables on the 2.6 timeframe.