Jasig is proud to announce the second Release Candidate of uPortal 3.2.0. This release is feature complete and will be undergoing additional testing and bugfixes over the next week before the general audience release is cut. The uPortal 3.2 release includes many new features contributed back by uPortal adopters along with the updates from nearly a year of production use. At this time parties interested in new uPortal deployments are encouraged to strongly consider starting with uPortal 3.2.

       New Feature

   * UP-2047 <http://www.ja-sig.org/issues/browse/UP-2047> - Create
     administrative portlet for managing channels
   * UP-2503 <http://www.ja-sig.org/issues/browse/UP-2503> - Use mFSS
     to create a mobile theme
   * UP-2578 <http://www.ja-sig.org/issues/browse/UP-2578> - Add Jasig
     Widget Portlets to uPortal
   * UP-2586 <http://www.ja-sig.org/issues/browse/UP-2586> - Add config
     mode for SQL portlet


       Improvement

   * UP-2564 <http://www.ja-sig.org/issues/browse/UP-2564> - Refactor
     fluid css to use distributed files and overlays
   * UP-2579 <http://www.ja-sig.org/issues/browse/UP-2579> - Support
     excluding portal events by username
   * UP-2581 <http://www.ja-sig.org/issues/browse/UP-2581> - Add API to
     look up user ID by username
   * UP-2582 <http://www.ja-sig.org/issues/browse/UP-2582> - Cache
     lookup of guest user id
   * UP-2583 <http://www.ja-sig.org/issues/browse/UP-2583> - Add Spring
     App Context Shutdown Hooks
   * UP-2584 <http://www.ja-sig.org/issues/browse/UP-2584> - Add
     EhCache regions for hibernate queries


       Task

   * UP-2566 <http://www.ja-sig.org/issues/browse/UP-2566> - Review
     EHCache configuration
   * UP-2569 <http://www.ja-sig.org/issues/browse/UP-2569> - Update to
     released verion of resource server
   * UP-2570 <http://www.ja-sig.org/issues/browse/UP-2570> - Update to
     released version of CAS proxy test portlet
   * UP-2571 <http://www.ja-sig.org/issues/browse/UP-2571> - Update to
     released version of Functional Tests Portlet
   * UP-2572 <http://www.ja-sig.org/issues/browse/UP-2572> - Update to
     released version of Web Proxy Portlet
   * UP-2574 <http://www.ja-sig.org/issues/browse/UP-2574> - Don't
     deploy EAR or WAR overlays to Maven
   * UP-2587 <http://www.ja-sig.org/issues/browse/UP-2587> - Add
     Weather Portlet
   * UP-2588 <http://www.ja-sig.org/issues/browse/UP-2588> - Deprecate
     IChannel
   * UP-2589 <http://www.ja-sig.org/issues/browse/UP-2589> - Switch to
     Apache 2.0 License


       Bug

   * UP-2525 <http://www.ja-sig.org/issues/browse/UP-2525> - Ivy skin -
     portlet chrome broken and other rendering issues
   * UP-2567 <http://www.ja-sig.org/issues/browse/UP-2567> - Exceptions
     thrown during layout import don't cause import to fail
   * UP-2568 <http://www.ja-sig.org/issues/browse/UP-2568> - Request
     encoding is not correctly set
   * UP-2573 <http://www.ja-sig.org/issues/browse/UP-2573> - Portlet
     preferences don't show in portlet manager review screen
   * UP-2575 <http://www.ja-sig.org/issues/browse/UP-2575> - Exception
     when clicking on portlet link after session timeout:
   * UP-2576 <http://www.ja-sig.org/issues/browse/UP-2576> -
     isUserInRole should allow for group name
   * UP-2580 <http://www.ja-sig.org/issues/browse/UP-2580> - Potential
     NPE when logging ChannelTargetedInLayoutPortalEvent
   * UP-2585 <http://www.ja-sig.org/issues/browse/UP-2585> - Canceling
     configuration of web proxy portlet results in stack trace

This release is indented to be feature complete and API stable. That said there is always the possibility that a bug fix in a RC could cause incompatibility with the GA release.

If you find an issue with this RC please report it in Jira <http://www.ja-sig.org/issues/secure/CreateIssue.jspa?pid=10020&issuetype=1>, issues in Jira are how we ensure the bugs are actually addressed.

*Important Upgrading Note*
uPortal 3.2.0 has had database changes that are incompatible with the previous releases. Upgrading to uPortal 3.2.0 will require using the crn-export scripts in your current install and then the crn-import scripts in your new uPortal 3.2.0 install. Pointing a uPortal 3.2.0 release at an older database will very likely not work and could cause database corruption.

Downloads are available from: http://www.jasig.org/uportal/download/uportal-320-RC2 Release notes are available at: http://www.ja-sig.org/wiki/display/UPC/3.2.0-RC2

uPortal Project Lead,
-Eric Dalquist

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to