Support for DSpace 5 ended on January 1, 2023. See Support for DSpace 5 and 6 is ending in 2023 |
DSpace 5.0 can be downloaded immediately from: See the DSpace 5.x Release Notes for more information. |
DSpace 5.x Release Notes have been incorporated into the DSpace 5.x documentation wiki. The content of that page, and this one, is similar, but it's not a perfect duplicate. This page is for coordinating and planning DSpace Release 5.0, and for communicating this status information to the community. This Release Status page is a historical document, with much of the same material. |
Table of Contents:
|
This has now been done in . This section is kept for archival purposes only. |
Solr is distributed on Maven Central as a .war file, which includes the Lucene .jars. No Lucene version relevant to DSpace is available from Maven Central.
Solr is a wrapper for Lucene providing concurrency. Lucene can work with index files directly if we don't need concurrent access (i.e. before we start up Solr).
DSpace 1.6 was the first version to use Solr for statistics. In order to upgrade to DSpace 5, we need to upgrade the Solr index format in two steps. The second step is easy, upgrading from DSpace 3 (Solr 3.5) to DSpace 5 means just running the Solr 4.10.2 optimize command, which can be run even concurrently when the UIs are running. However, Solr 4.4 doesn't understand the legacy index formats used in Solr before 3.5. Therefore, in the first step, we need to use Solr 3.5 or Lucene 3.5 to upgrade from the older index versions to 3.5.
We need to avoid the conflict of having both Solr 3.5 and 4.10.2 in the DSpace classpath. Therefore I suggest to run the first step before the Solr 4.10.2 webapp is started as part of DSpace 5.
To do that, we need to:
The manual steps would be:
wget "http://search.maven.org/remotecontent?filepath=org/apache/lucene/lucene-core/3.5.0/lucene-core-3.5.0.jar" -O lucene-core-3.5.0.jar # check index version, see table below: java -cp lucene-core-3.5.0.jar org.apache.lucene.index.CheckIndex /dspace/solr/statistics/data/index/ java -cp lucene-core-3.5.0.jar org.apache.lucene.index.CheckIndex /dspace/solr/search/data/index/ # upgrade index version: java -cp lucene-core-3.5.0.jar org.apache.lucene.index.IndexUpgrader /dspace/solr/statistics/data/index/ java -cp lucene-core-3.5.0.jar org.apache.lucene.index.IndexUpgrader /dspace/solr/search/data/index/ # check index version again, should be "version=3.5 format=FORMAT_3_1 [Lucene 3.1+]" |
DSpace | Solr | Lucene | Used Lucene index version | version reported by CheckIndex | Supported Lucene index versions |
5.0 | 4.10.1 | 4.10.2 | 4.10 | (before optimize) versions=[4.4.0 .. 4.10.2] format= | |
4.0 | 4.4.0 | 4.4 | 4.4 | version=4.4.0 format= | |
3.0 | 3.5.0 | 3.5 | version=3.5 format=FORMAT_3_1 [Lucene 3.1+] | LUCENE_20, LUCENE_21, LUCENE_22, LUCENE_23, LUCENE_24, LUCENE_29, LUCENE_30, LUCENE_31, LUCENE_32, LUCENE_33, LUCENE_34, LUCENE_35 | |
1.8 | 3.3.0 | 3.3 | ??? | version=3.3 format=FORMAT_3_1 [Lucene 3.1+] | |
1.7 | 1.4.1 | 2.9.3 (2.9.3 951790 - 2010-06-06 01:30:55) | ??? | version=FORMAT_DIAGNOSTICS [Lucene 2.9] | |
1.6 | 1.3.0 | 2.4-dev (2.4-dev 691741 - 2008-09-03 15:25:16) | ??? |
https://code.google.com/p/luke/wiki/Compatibility
Java version
Minimum version of JVM required to run Luke 1.0.1 and earlier is 1.5.
Minimum version of JVM required to run Luke 3.x and 4.x is 1.6.
Lucene Java indexes
Luke 1.0.1 should be able to open indexes built using the following versions of Lucene-Java:
Starting with version 4.x Luke cannot open indexes created with Lucene 3.0.0 or earlier.
Starting with version 3.1.0 Luke releases will use the same numbering as Lucene releases, to avoid confusion.
The following changes have already been made to the codebase and will be released in 5.0. Please note that the below listing is dynamically generated, so it will be changing as we continue to add new features, improvements and bug fixes to the 5.0 release.
Instead of a single "Release Coordinator", the DSpace 5.0 release will be managed by a "Release Team".
All Release Team membership information is as of November 4, 2014. Please volunteer (by emailing Tim Donohue), if you are interested in joining the team!
Your contributions are welcome now! Code and documentation need not be finished, so long as it is working and we can all see what it is for. Time is set aside for fixing, polishing, and integration. We have some general Code Contribution Guidelines available, but you are also welcome to ask questions on the dspace-devel mailing list.
Date | Milestone | What it means |
---|---|---|
October 06 | Deadline for feature pull requests | If you wish to contribute features to DSpace 5.0, you must submit a pull request by this date. |
October 08 | Weekly developers' meeting devoted to review of feature pull requests for 5.0 | The entire hour's meeting will be used to discuss proposed features submitted by the deadline. |
October 15 | Weekly developers' meeting devoted to review of feature pull requests for 5.0 | The entire hour's meeting will be used to discuss proposed features submitted by the deadline. |
October 31 | Feature freeze | DSpace 5.0 is considered feature-complete on this date. Only bugfixes will be pulled between this date and final release. |
November 6 | Release Candidate 1 tagged | A DSpace 5.0 Release Candidate will be available for wider testing. |
November 10 | Release Candidate 2 tagged | 5.0-rc2 was released to address missing optional artifacts from 5.0-rc1 (Mirage2 and LNI) |
November 10-21 | Testathon | Intensive public testing of the 5.0 Release Candidate is invited. The Release Team will focus on getting problems resolved. |
December 19 | Release Candidate 3 tagged | An updated DSpace 5.0 Release Candidate will be available for wider testing. |
January 15 | DSpace 5.0 is publicly released | DSpace 5.0 is released for download and general use. |
Release Process needs to proceed according to the following Maven release process: Release Procedure