Page History
Version 3.0
...
Warningnote | ||
---|---|---|
| ||
With DSpace 3.0, the DSpace Developers will be changing our release numbering scheme. Release numbers will now only consist of two numbers:
For more information see: Release Numbering Scheme | ||
| ||
We recommend users upgrade to DSpace 3.2 directly, rather than upgrading to 3.0. The process to do so is documented at: DSpace Release 3.2 Notes |
Tipinfo | ||
---|---|---|
| ||
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! |
...
| |
DSpace 3.0 can be downloaded immediately at either of the following locations:
|
Table of Contents:
Table of Contents | ||||||||
---|---|---|---|---|---|---|---|---|
|
Why 3.0? What happened to 2.0?
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:
- The history of discussions around DSpace "2.0" has have gone through many different lists of proposed features revisions over the past 8 years:
- Discussion of "2.0" first began in 2004, with Robert Tansley's DSpace 2.0 Original Proposal
- A reworking of the "2.0" concept happened in 2006, during a DSpace Architectural Review.
- A further reworking of the "2.0" concept occurred in 2008-2009 when a prototype version of DSpace 2.0 was built and demoed at Open Repositories 2009.
- As detailed in the 2.0 history above, much of the planning around a "2.0" is now many years old. Although many great ideas/concepts have come out of that work, much of it does need to be reanalyzed for the modern repository environment.
- "2.0" has always been talked about as a "revolutionary" change to the DSpace software platform. In reality, we've found that many of these the platform improvements attributed to "2.0" have been incremental in nature and have been included over many releases (for example, nearly every major release in recent years has included some . In fact, several 2.0 code/concepts (from the 2009 DSpace 2.0 Prototype) have been included in almost every recent major release.
- Because the "2.0" release has a perception of been perceived as being "revolutionary" in nature, it would be difficult to ever fully meet the expectations/assumptions that have built up around this release over time.
- We all feel that the DSpace Community's immediate needs are better met by incremental changes (over several releases) than by revolutionary changes (over a single release). We feel that incremental changes provide an easier upgrade path between current and future releases of DSpace.
Therefore, many 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.
...
Note | ||
---|---|---|
| ||
With DSpace 3.0 |
...
, the DSpace Developers will be changing our release numbering scheme. Release numbers will now only consist of two numbers:
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 |
New features in DSpace 3.0
Excerpt | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
Additional information about DSpace 3.0 may be found in the 3.0 Documentation. A full list of all changes / bug fixes in 3.0 is available in the History section of the 3.0 Documentation. |
(All non-commercial images in the above table are free-to-use images borrowed from elsewhere. In order: OAI-PMH image, chart image, import icon, dictionary icon, key icon, magnifier icon, documents icon, lock icon, phone icon)
Upgrade Instructions
- If you are upgrading from 1.8.x to 3.x, please see Upgrading From 1.8.x to 3.x
- For general upgrade instructions, please see Upgrading a DSpace Installation
Organizational
Note | ||
---|---|---|
| ||
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.
- Various features from the Dryad Project (based on DSpace)? May or may not include the following:
- Item-level Versioning
- Dryad Example: Version 1, Version 2 of same document (see versions listed at bottom of page)
- Codebase: https://dryad.googlecode.com/svn/trunk/dryad/dspace/modules/versioning/
- Support for additional External Identifier Services (e.g. DOI, etc.)
- Dryad Example: The same document can be accessed via different identifiers: DOI link (http://dev.datadryad.org/resource/doi:10.5061/dryad.1385.2
), Handle link (http://dev.datadryad.org/resource/info:hdl/10255/dryad.36265
), default DSpace Link (http://dev.datadryad.org/resource/10255/dryad.36265
)
- Codebase: http://code.google.com/p/dryad/source/browse/trunk#trunk%2Fdryad%2Fdspace%2Fmodules%2Fidentifier-services
- Dryad Example: The same document can be accessed via different identifiers: DOI link (http://dev.datadryad.org/resource/doi:10.5061/dryad.1385.2
- Item-level Versioning
...
Details
Release Coordination
Instead of a single "Release Coordinator", the DSpace 3.0 release will be managed by a "Release Team".
Release Team Leader
...
MIT)
...
Release Team Members
...
Sands Fish (MIT), Hardy Pottinger (U of Missouri),
...
Robin Taylor (EDINA, U of Edinburgh), Ivan Masár
Timeline and Processing
Note |
---|
It has been decided that DSpace 3.0 will be released in Fall/Winter 2012. The exact date is still being worked out, but will likely be in October/November. |
- August 24, 2012 : Feature/Code Submission Deadline - New features must be submitted as a GitHub Pull Request by this date. Any new features submitted after this date will not be considered for 3.0.
- August 31, 2012 : Final Documentation Due Date - Initial documentation for all new features is due.
- September 14, 2012 : Feature Freeze - This is an internal deadline for the Committers. This is the date by which the Release Team and Committers will have reviewed via Pull Request, and accepted or rejected all contributions made for the 3.0 release. Rejected code has to wait for the next version of DSpace (or is suggested to be released separate from the current release as a "third party add-on", if applicable).
- October 8, 2012 : Release Candidate 1 is released
- October 10-19, 2012 : Test-a-thon
- October 22-31, 2012 : Bug fixing period
- October 24, 2012 : Release Candidate 2 is released
- October 25, 2012 : Release Candidate 2 is on demo.dspace.org
- October 24-November 1, 2012 : Testing / Bug Fixing
- November 1, 2012 : Release Candidate 3 is released
- November 5, 2012 : Release Candidate 3 is on demo.dspace.org
- November 5-9, 2012 : Test-a-thon (2nd round)
- November 9-25, 2012 : Testing / Bug Fixing
- November 30, 2012 : 3.0 Final Release
...
Release Process needs to proceed according to the following Maven release process: Release Procedure
3.0 Decisions To Be Documented
- Where should translations of individual modules like Discovery go? Including them in the main messages.xml currently works. This should be answered before freeze time, it already poses another barrier for commiting of translations, see DS-1049, DS-1054. This is a subproblem of i18n Improvements Proposal, but let us not divert this discussion too much to broad topics. ~~helix84
- 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])