Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Presentation Summary

The uPortal project has made significant progress for the 2.5 release and future plans for a 2.6 release. The uPortal 3 framework has also progressed significantly in the past 6 months and is on track for an initial release this fall. This presentation will cover the progress made with both frameworks along with an overview of the related discussion from the spring uPortal developers meeting.

Speakers:

See also the Winter 2004 uPortal Roadmap presentation.


Introduction (5 minutes, Andrew)

Major, Minor, and Patches releases

Major releases accomodate revolutionary change, such as moving from being IChannel-centric to being JSR-168 portlet-centric. Minor releases accomodate evolutionary change, such as moving to Commons Logging, adopting a new Layout Manager implementation. Patches releases accomodate conservative, backwards-compatible changes, such as most bugfixes.

Feel-good slides showing the many uPortal deployers

Patch releases provide backwards-compatible improvements, fixes for these current deployers. Minor releases provide incrementally enhanced versions of uPortal that aren't so very much different to which deployers might upgrade, new deployers might start out with. Introduce new features in response to deployer contributions, feedback. Major releases provide revolutionarily new platform upon which to build enterprise portal instances.

uPortal 2.x (20 minutes, Andrew)

uPortal 2.4.3

Important progress in 2-4-patches towards uPortal 2.4.3. Bugfixes. Memory leak fixes.

uPortal 2.5.0

What's in this release, what didn't make it, and what this means

SunGard SCT DLM Layout Management

  • Layout management from the commercial product Luminis

Improved JSR-168 support

  • Portlet caching
  • Redirects

Chaining Throwables throughout

Adoption of JDK 1.4, enhancement of our APIs, and actually chaining at the throws lead to pervasively chaining exceptions, making it easier to debug a running uPotal.

Release QA

Incrementally improved. All the unit tests pass.

Spring

Incremental adoption of Spring as the way we wire together a uPortal instance. (Transition to uP 3.0 portion of talk...)

uPortal 2.6

Predictions of another uPortal 2.x release

uPortal 3.0 and beyond (20 minutes, Eric)

Conclusion (5 minutes, Eric)

Questions (10 minutes, whoever can answer)

  • No labels