Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

With DSpace 3.0, the DSpace Developers will be changing our release numbering scheme. Release numbers will now only consist of two numbers: {{\[major\].\[minor\]}} (e.g. 3.0, 3.1, 4.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

Note
titleDSpace has changed its release numbering scheme

Wiki Markup

...

...

  • 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
      unmigrated-wiki-markup
    • 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?
      unmigrated-wiki-markup
    • 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
    • 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?)

...