Page History

...

So, to get to my point here... A part of me wonders if what we may want to work towards is something similar to the following:

Main Proposal/Idea:

• All "Core Infrastructure Modules" should sit in SVN Trunk, and be released synchronously, as they constitute a new release of DSpace, and should likely be versioned together (to ensure they can be tested together, and always undergo proper quality control, etc.)
• Most (maybe even all?) "Web UI/Web Services Modules" could potentially be stored external from SVN Trunk and released asynchronously. Obviously, some of the primary UIs or Web Services would also be released synchronously alongside any new release of DSpace.
  • Obviously, this may mean moving XMLUI, JSPUI, SWORD, etc. out of Trunk. This may or may not be controversial idea. But, to me it's more logical than storing "core apis" outside of Trunk. Mainly because, we know that these various UIs/interfaces will receive proper attention/testing come release time (in the form of Testathons, etc). Plus, it could potentially open the door to allowing users to install DSpace and "pick & choose" which UIs actually get installed alongside it (rather than getting all UIs installed at all times).

An example may be the best way to understand this idea! What I'm talking about is the following sort of release process (I've randomly chosen to call this release DSpace "11" so that it has no real meaning or implications. I could have just as easily called it DSpace "2011" or DSpace "Mountain Lion".)

...