Version 3.0 (Nov 2012)

...

DSpace

...

3.0

...

• Major Releases: incrementing the first number ('major') will represent a new MAJOR release of DSpace. A major release may include any or all of the following: 
  
  • new features
  • system improvements
  • architectural changes
  • bug fixes 
  • (All major releases end in ".0", so "3.0", "4.0", and "5.0" would all represent major releases.)
• Minor (Bug-Fix) Releases: incrementing the second number ('minor') will represent a new MINOR release of DSpace. A minor release will only include: 
  
  • bug fixes to an existing major release (For example, "3.1" and "3.2" would represent two minor releases which only include bug fixes to the "3.0" major release.)

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

was officially released to the public on November 30, 2012.

DSpace 3.0 can be downloaded immediately at either of the following locations:

• SourceForge (Zip): https://sourceforge.net/projects/dspace/files/
• GitHub: https://github.com/DSpace/DSpace (tag 'dspace-3.0')

In addition, you are welcome to try out DSpace 3.0 on http://demo.dspace.org/ and continue to provide any feedback you may have.

Why 3.0? What happened to 2.0?

...

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.

New features in DSpace 3.0

...

(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)

Organizational 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

• 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

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])

...