[Deploying Sakai] Release announcement: Profile2 1.3.15

[Steve Swinsburg]

I am proud to announce a new release of Profile2 in the 1.3 series.

Version:
Profile2 1.3.15

Description:
Profile2 is a complete re-design and re-development of the existing Profile tool in Sakai. It gives you more of a Facebook style interface for editing your profile.
In addition you have a comprehensive set of Privacy controls to allow you to choose who can see what part(s) of your Profile.

With Profile2 you can post updates (integrated with Twitter), search for people with common interests, view their profiles, view their connections,
add them as a connection, and much more.

Profile2 can be run seamlessly alongside the existing profile in Sakai and integrates with the Roster tool.

Works with:
Sakai 2.4, 2.5, 2.6, 2.7, 2.8

Database upgrade:
There is no database upgrade required that is specific to this release. However, there have been two previous database upgrades required for the 1.3.x release series. You should ensure you have applied both the 1.3.x-1.3.9 and 1.3.x-1.3.14 upgrade scripts, located in the docs/database directory, or here if you are using a binary deployment: 
https://source.sakaiproject.org/svn/profile2/tags/profile2-1.3.15/docs/database/
Please note that a bug exists in the Oracle version of the 1.3.x-1.3.9 upgrade script which is present in 1.3.9. This has been fixed so you should use the version bundled in the 1.3.10 release or later.

Availability:
	SVN: https://source.sakaiproject.org/svn/profile2/tags/profile2-1.3.15/
	Binaries: https://source.sakaiproject.org/maven2/org/sakaiproject/profile2/

	Deployers running Sakai 2.7 should perform the following steps to upgrade:
		1. Update the <sakai.profile2.version> in $SAKAI_SRC/master/pom.xml to 1.3.15
		2. Remove profile2-help-.jar and profile2-api-.jar from $CATALINA_HOME/shared/lib
		3. Rebuild/redeploy the core-deploy project to fetch the new release and install it into Tomcat
		4. Apply any database patches as necessary

	Deployers building from source should perform the following steps:
		1. Checkout the 1.3.15 tag using the SVN link above
		2. Remove profile2-help-.jar and profile2-api-.jar from $CATALINA_HOME/shared/lib
		3. Build and deploy the 1.3.15 tag
		4. Apply any database patches as necessary

Highlights:
This is a maintenance release which fixes an issue identified in the 1.3 branch, related to the display of remote profile images in other tools such as the Roster and Clog. It also fixes a socket exception associated with the same issue, when a Sakai instance is served via SSL and a remote profile image is requested.

For full details of the features and fixes in this release, see:
http://jira.sakaiproject.org/secure/IssueNavigator.jspa?reset=true&pid=10500&fixfor=12308

And as always, for full installation and configuration instructions, see:
http://confluence.sakaiproject.org/display/PROFILE/Profile2

Known issues:
If a user has no profile image, and the Roster integration is activated, then the Roster will show the default image 'No Official Photo is Available' even if official photos are not being used. This text could be misleading to some. The fix is to simply replace the image that Roster ships with to be the generic 'no image' from Profile2. This may be addressed in a future release.

Acknowledgements:
Thanks to the following Sakai community members (in no particular order) for their involvement in this release:

Jean-Francois Leveque
Raad Al-Rawi

License:
Profile2 is released under the Educational Community License Version 2.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20110411/e48732e4/attachment.html