Version 1.8.0

DSpace 1.8.0 is a scheduled, "time-based" release. In order to decrease delays in releasing new features and increase transparency, the DSpace Developers have scheduled 1.8.0 in advance and are basing its features on what we are able to complete within that timeframe.

Scheduling releases benefits us all as it should decrease the delays in releasing new features, and increase the transparency of the development process. The DSpace Developers feel that these benefits will far outweigh the cost of potentially having fewer major features in a given DSpace release. We hope the DSpace Community will also realize the immediate benefits, which should allow them to receive new features more quickly, rather than potentially waiting years for the next major release of the software. The DSpace Developers hope to continue this trend of "time based" releases with all future releases.

New features in DSpace 1.8

New Features are yet to be determined. If you have ideas or code you'd like to see make it into DSpace 1.8.0, please submit it to our Issue Tracker

For a list of all features/improvement/bugs currently scheduled for 1.8.0, see the 1.8.0 Version in our Issue Tracker.
NOTE: This listing is not finalized, and is likely to change. Not all features/improvements/bugs currently scheduled for 1.8.0 are guaranteed to be in that release.

Organizational Details

Release Coordination

Release Coordinator: TBA - We still need volunteer(s) to act as Release Coordinator

Timeline and Proceeding

RELEASE TIMELINE IS NOT FINALIZED! Two Release Timelines have been proposed and are currently being decided upon by the Committers.

First a few definitions:

"Beta" releases - These are a newly proposed idea for 1.8.0. Essentially a "Beta" release would be an early release of the software, even before all features are finalized. They give developers an opportunity for early feedback from the community or other developers around a new feature. Only features that are into Trunk at the time will be released into the Beta Release. After and between Beta releases, features may change.
"Release Candidate" releases - These are initial releases after all features have been finalized. Features may not change, but bug fixes can be made.

Proposed Release Timeline #1 - 9 months (same timeframe as 1.6.0 to 1.7.0)
- May 13, 2011 : Beta 1
- June 3, 2011 : Beta 2 (Note: OR11 is June 7-11)
- July 22, 2011 : Feature Freeze
- July 29, 2011 : Final Documentation "Due Date"?
- August 5, 2011 : Release Candidate 1
- August 8-19, 2011 : Testathon
- September 2, 2011 : Release Candidate 2
- September 5-14, 2011 : Final Testing / Bug Fixing
- September 16, 2011 : Final Release

Proposed Release Timeline #2 - 10 months (slightly longer timeframe, but if we moved to 12 months timeframe afterwards, then we'd just do a new release every October, before the holidays get started)
- June 3, 2011 : Beta 1 (Note: OR11 is June 7-11)
- July 8, 2011 : Beta 2
- August 19, 2011 : Feature Freeze
- August 26, 2011 : Final Documentation "Due Date"?
- September 2, 2011 : Release Candidate 1
- September 5-16, 2011 : Testathon
- September 30, 2011 : Release Candidate 2
- October 3-12, 2011 : Final Testing / Bug Fixing
- October 14, 2011 : Final Release

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