uPortal developers, It's been more than a month since the June 11th uPortal 4.0.14 release and goodness has accumulated since then in the 4.0-patches branch, so I think it's time to think about cutting a 4.0.15 release.
Does anyone have work in-flight for the 4.0.15 release that ought to hold up freezing for and cutting that release? I'm aware of a potential security issue working through the Apereo uPortal security issue process that may result in a fix for the 4.0 release series -- this email thread isn't about that and is rather about the normal, public 4.0.x release process that uPortal developers might fruitfully discuss right here on uportal-dev@. As things stand, 4.0.15 if soon cut might include that not-yet-public fix as well as the goodness accumulated in 4.0-patches since 4.0.14, namely: * Fix Maven build issues to better handle 301 redirects in retrieving resources. * SimpleContent upgrade to 1.0.9 and start using a validation query on its connection pool. * hsql configuration to use more ample memory * travis-ci continuous integration builds of the 4.0-patches branch. * Clearpass clustering configuration and logging improvements * Remove the acceptAnyProxy configuration on the ClearPass endpoint in the CAS server shipping with uPortal (introduced in 4.0.14) in the fervent hope that no one will accidentally put that acceptAnyProxy configuration into production service. Kind regards, Andrew -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
