Versions Compared

Old Version 12

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 13

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 module versioning we do, the more confusing Q&A on listservs may be. E.g., when answering a question on DSpace Services, how does one easily remember that Services 2.0.3 was in DSpace 1.7.1, but Services 2.0.2 was in DSpace 1.7.0. This may get more complex as more core modules are versioned separately
  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 our users may wish to see released asynchronously versus as part of a "packaged" release.
  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 consistent quality control of all these asynchronously released modules (i.e. when/how does more thorough testing happen for asynchronous releases)?

...