Versions Compared

Old Version 2

changes.mady.by.user Mark Diggory

Saved on

compared with

New Version Current

changes.mady.by.user Tim Donohue

Saved on

Key

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

This proposal has now been accepted. The DSpace Developers moved towards Time-Driven Releases with 1.7.0 Release, and plan to continue that process for the foreseeable future.

Excerpt
hiddentrue

Proposal to move to regular, recurring releases on a schedule. (Reviewed on 10 March 2010 during DSpace Dev Mtg – see page for comments)

Issue Addressed

Consider the time sequence of DSpace major releases (dates approximate):

...

  1. Mark Diggory and Graham Triggs would like us to also support asynchronous releases. For example, releasing just a 1.7.1 'dspace-api' module, if bugs only affect the 'dspace-api' (and not waiting for a full 1.7.1 release). How does this fit into time-driven releases? Could it be complimentary or does it require changes to this time-driven release idea?
  2. If we were to approve this time-driven release idea, what sort of time-frame would we want to set? One major release per year? Two major releases per year?
    • For the time being, we've decided to schedule the 1.7.0 Release for Dec 2010. After 1.7.0 is released, we'll decide on an ongoing release schedule based on the experiences with releasing 1.7.0.