DSpace 3.2 was officially released to the public on July 24, 2013.
DSpace 3.2 can be downloaded immediately at either of the following locations:
SourceForge (Zip): https://sourceforge.net/projects/dspace/files/
GitHub: https://github.com/DSpace/DSpace (tag 'dspace-3.2')
In addition, you are welcome to try out DSpace on http://demo.dspace.org/ and continue to provide any feedback you may have.
We recommend DSpace 3.x users upgrade to 3.2
Generally we recommend all DSpace 3.x users upgrade to DSpace 3.2 to receive several bug fixes. However, if you decide that none of the bug fixes are relevant for you then there is no urgent case for upgrading.
However, it is worth noting that DSpace 3.2 includes a security fix for the JSPUI. Therefore, we highly recommend anyone using the JSPUI upgrade to DSpace 3.2.
DSpace 3.2 is a bug fix / security fix release to resolve any issues located within DSpace 3.0 or DSpace 3.1. As it only provides bug-fixes, DSpace 3.2 should constitute an easy upgrade from DSpace 3.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 3.x to 3.2.
This small bug fix release addresses a number of issues that have cropped up in 3.x. These issues include:
- Several bug fixes to the OAI-PMH interface
- Resolved memory leak in JSPUI
- Resolved security issue in JSPUI (DS-1603 - requires a JIRA account to access)
- Several minor configuration / build fixes
- Other minor fixes (see below)
- For upgrade instructions for 3.x to 3.2, please see Upgrading From 3.0 to 3.x.
- If you are upgrading from 1.8.x to 3.2, please see Upgrading From 1.8.x to 3.x
- For general upgrade instructions, please see Upgrading a DSpace Installation
No new features in DSpace 3.2
The following fixes were released in 3.2.
This release also included a security fix (which requires a JIRA account to view):
- DS-1603 - Resolves a security issue in JSPUI
- Release Coordinator: Committers Team (shared coordination) led by Hardy Pottinger
Timeline and Proceeding
- Release Date: July 24, 2013
Release Process will proceed according to the following Maven release process: Release Procedure