There will be a migration path for users upgrading from v1.8.2 to the 3.0 release. For more information see DSpace Release Numbering Scheme and the initial DSpace 3.0 Announcement |
In order to decrease delays in releasing new features and increase transparency, the DSpace Developers have scheduled 3.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. Want to contribute to this release of DSpace? Please see the How to Contribute to DSpace page for ways that you can help out! |
In 2011, after much discussion, the DSpace Committers in conjunction with members of the DSpace Community Advistory Team (DCAT) decided to forgo releasing a "DSpace 2.0".
The reasons for this decision were numerous and include:
Many of the ideas/concepts of "DSpace 2.0" may still be coming to the DSpace platform. But, they will continue to be added incrementally over several releases. The ideas behind "2.0" still live on, even while the release numbering has changed.
If you have ideas or code you'd like to see make it into DSpace 3.0, please submit it to our Issue Tracker. |
Developers: Add what you are working on to this list. Please try and link off to additional documentation (on Wiki) or related JIRA issues.
\[[DS-1144\]|https://jira.duraspace.org/browse/DS-1144] Maven Project Consolidation |
\[[DS-1229\]|https://jira.duraspace.org/browse/DS-1229] Discovery Enhancements ([Pull Request|https://github.com/DSpace/DSpace/pull/45]) |
-HTML pages for OAI generated with client-side XSLT (--[doc|https://wiki.duraspace.org/display/DSDOC3x/OAI#OAI-EnablingOAIPMHInterface]--,- -[DS-1178|https://jira.duraspace.org/browse/DS-1178]--) \[COMMITED\]- Lyncode's OAI 2.0 does it better (see below) |
SFX button support (institutional branding) ([doc|https://wiki.duraspace.org/display/DSDOC3x/Configuration#Configuration-JSPUI%2FXMLUISFXServer], [DS-820|https://jira.duraspace.org/browse/DS-820]) \[COMMITED\] |
robots.txt: disallow indexing some dynamically generated pages ([DS-1138|https://jira.duraspace.org/browse/DS-1138]) \[COMMITED\], documentation on robots.txt desirable |
3.0 Decisions To Be Documented:
ANSWER: In mtg on July 25, we decided the best we likely can do for 3.0 is to suggest that translations of individual modules should just be added to the central messages.xml/messages.properties files. For the full discussion see: [http://irclogs.duraspace.org/index.php?date=2012-07-25] (starts: \[20:57\]) |
ANSWER: Yes, it seems to work with *both* Oracle JDK 7 and OpenJDK 7. We should test & document it works for both. For full discussion see: [http://irclogs.duraspace.org/index.php?date=2012-07-25] (starts: \[20:13\]) |
Please note the lists of accepted changes below are dynamically generated from our ticketing system (JIRA). This list may change at any time, and is not finalized until DSpace 3.0 is formally released. |
Instead of a single "Release Coordinator", the DSpace 3.0 release will be managed by a "Release Team".
It has been decided that DSpace 3.0 will be released in Fall 2012. The exact date is still being worked out, but will likely be in October/November. |
Release Timeline (PROVISIONAL):
August 17, 2012 : Feature Freeze Date
August 24, 2012 : Final Documentation "Due Date"?
August 31, 2012 : Release Candidate 1 Release
September 4-14, 2012 : Testathon
September 28, 2012 : Release Candidate 2 Release
October 1-10, 2012 : Final Testing / Bug Fixing
October 12, 2012 : 3.0 Final Release
Release Process needs to proceed according to the following Maven release process: Release Procedure