Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

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

Compare with Current View Page History

« Previous Version 4 Next »

Version 1.7.3

DSpace 1.7.3 was officially released to the public on July 25, 2013.

DSpace 1.7.3 can be downloaded immediately at either of the following locations:

All DSpace 1.7.x JSPUI users should upgrade to 1.7.3

DSpace 1.7.3 includes a security fix for the JSPUI. Although there are no known exploits, we recommend all 1.7.x JSPUI users upgrade to 1.7.3 in order to fix this vulnerability.

Summary

DSpace 1.7.3 is a security fix release to resolve a JSPUI security vulnerability in the 1.7.x platform.

This security release includes the following fixes:

  • Resolved security issue in JSPUI (DS-1603 - requires a JIRA account to access)
  • Minor cleanup of the 1.7.x codebase so that it is Git/GitHub friendly. This means that 1.7.3 can now be forked or checked out from GitHub, using either Git or Subversion

We highly recommend all 1.7.x JSPUI users upgrade to 1.7.3.

For upgrade instructions for 1.7.x to 1.7.3, please see Upgrading From 1.7 to 1.7.x.

No new features in DSpace 1.7.3

1.7.3 is a security fix release. This means it includes no new features.

For a list of all new 1.7 Features, please visit the DSpace Release 1.7.0 Notes.

Bug Fixes

Changes

The following fixes were released in 1.7.3.

key summary assignee reporter

Data cannot be retrieved due to an unexpected error.

View these issues in Jira

This release also included a security fix (which requires a JIRA account to view):

  • DS-1603 - Resolves a security issue in JSPUI

Organizational Details

Release Coordination

  • Release Coordinator: Committers Team (shared coordination) led by Hardy Pottinger

Timeline and Proceeding

Release Timeline:

  • Release Date: July 25, 2013.

Release Process will proceed according to the following Maven release process: Release Procedure

  • No labels