Page History
...
New features in DSpace 3.0
...
DSpace 3.0 ships with a number of new features. Certain features are automatically enabled by default while others require deliberate activation.
The following non-exhaustive list contains the major new features in 3.0 that are enabled by default:
...
| Jira | ||||
|---|---|---|---|---|
|
...
| Jira | ||||
|---|---|---|---|---|
|
...
Kindly contributed by Lyncode | |
 |
Kindly contributed by @mire |
 |
...
...
|
...
Kindly contributed by the Greek National Documentation Centre EKT | |
...
| Google Analytics support for JSPUI |
...
The following list contains all features that are included in the DSpace 3.0 release, but need to be enabled manually.
Review the documentation for these features carefully, especially if you are upgrading from an older version of DSpace.
 |
|
 |
Kindly contributed by @mire with support of MBLWHOI Library and Dryad |
 |
Kindly contributed by @mire with support of the University of Michigan Libraries |
 | DSpace Mobile Theme (beta) Kindly contributed by Miami University Ohio |
|
...
| Jira | ||||
|---|---|---|---|---|
|
...
LDAPHierarchicalAuthentication superseded by LDAPAuthentication; new Authentication Plugins#login.groupmap option added
A full list of all changes / bug fixes in 3.0 is available in the History section or in the list of "Accepted Changes" below.
Accepted Changes
| Note |
|---|
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.
| Jira Issues | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Jira Issues | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Jira Issues | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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])
...
Does 3.0 Work with Java 7?
...
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])
...
Actually, I read the log again and nobody said they're running specifically OpenJDK version 7, but I agree we should support it (I will run it when I upgrade my systems). ~~helix84
...
UPDATE: demo.dspace.org is running OpenJDK 7
...
We recently added a comment on ticket DS-1081 reporting the problems we faced with Oracle JDK 7 (and OpenJDK 7) and the XmlWorkflow. It'd be great if someone could test it and confirm it.
...
Do we need to bump up required/recommended versions of any dependencies? (e.g. Maven, Postgres?)
Release Schedule Details
Release Coordination
Instead of a single "Release Coordinator", the DSpace 3.0 release will be managed by a "Release Team".
Release Team Leader: Sands Fish (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 2012. The exact date is still being worked out, but will likely be in October/November.
Release Timeline:
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 26/27, 2012 : 3.0 Final Release
Release Process needs to proceed according to the following Maven release process: Release Procedure
Overview
Content Tools