Versions Compared

Old Version 5

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 6

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. We've already seen discussions on lists (see, e.g. Services thread on dspace-devel) around confusion caused by some modules being only in the "/modules" area of SVN (e.g. Services)
  2. I worry that the more separate versioning we do, the more confusing Q&A on listservs may be. E.g., how easy will it be to keep track of which version of "Services" or various other core modules is in DSpace "8.0" (or any other version).
  3. Although the idea of asynchronous releasing everything (i.e. all modules) sounds nice to Developers, I worry that it really won't get much interest from 95% or more of our users (who generally are not developers, though they may have part time of a developer on staff). In reality, maybe it'd be better to draw lines between what is released asynchronously and what is released synchronously.
  4. If we move towards asynchronously releasing everything, I'm worried "quality control" may decrease. How would we, as a trusted group of developers, be able to ensure quality control , while also supporting some asynchronous processesof all these asynchronously released modules?

Goals of this Proposal

The goals of this proposal are to re-think the idea of "asynchronous releases", specifically:

...