Page History

In no particular order, here are some hints/tips to help introduce a new Committer to the DSpace Development process:

...

• GitHub - The main codebase is now here. See Development with Git for some hints/tips.
• JIRA - Obviously this is where we log all bugs/tickets. It is also used to auto-generate the "History" page of our DSpace Documentation, e.g. 1.8 History page
• Bamboo - We use Atlassian Bamboo tool for automatic building/testing of any new commits to GitHub. If an error occurs during an automated build/test, then an email is set to the dspace-changelog listserv. More info at: ContinuousIntegration
• DSpace Wiki- The public wiki space. A few areas to be aware of (if you are not already)
  • Committer Guidelines - Splash page for all our Committer Guidelines. We try to keep this as up-to-date as possible. But, if you have questions, please ask!
  • Release Procedure - In case you are interested, this is our procedure for cutting a new release.
• DSpace Documentation DSDOC- The official DSpace documentation is created in the wiki (and PDFs are generated from the wiki during releases). This is the splash page which lists all the existing DSpace Wiki Documentation.
  • How we generally manage this Documentation is on a subpage: Documentation Management
• SourceForge - These days, SourceForge is primarily used for two purposes: (1) it hosts all of our mailing lists, and (2) we post all releases up there for download.
• demo.dspace.org- The demo installation of DSpace which is on a virtual server (Amazon EC2 w/Ubuntu Linux). This server is used to show off the latest version of DSpace, as well as to help test upcoming features during release Testathons.
  • Any Committers can request command-line access to this server (to start/stop the instance, upgrade it, etc) by sending your Public SSH Key to Tim (or to any other Committer who already has command-line access to this server).
• www.dspace.org - Main website which is managed by DuraSpace. If you need something changed/updated there, contact Tim or email sysadmin at duraspace.org

...

• DSpace- The main codebase.
  
  • The "master" branch is where development for the next major version of DSpace happens
  • The various other branches (e.g. 'dspace-1_8_x') are "maintenance branches"
  • The tags (e.g. 'dspace-1.8.0', 'dspace-1.8.1', 'dspace-1.8.2') are the official stable releases of the software
• dspace-services - The DSpace Services Framework, which is prior to DSpace 3.0 was released separately to Maven Central (so DSpace can could use it as a dependency & include it out-of-the-box). It is now released and maintained as part of DSpace.
• dspace-api-lang - The DSpace API/JSPUI Language Packs, which are released separately to Maven Central (so DSpace can use it as a dependency & include it out-of-the-box)
• dspace-xmlui-lang - The DSpace XMLUI Language Packs, which are released separately to Maven Central (so DSpace can use it as a dependency & include it out-of-the-box)
• dspace-solr - Special, slightly customized version of Solr, which is released separately to Maven Central (so DSpace can use it as a dependency & include it out-of-the-box)
• dspace-cocoon-servlet-service-impl - Patched version of Cocoon Servlet Service which resolves issues with Cocoon swallowing 404 Errors, which is released separately to Maven Central (so DSpace can use it as a dependency & include it out-of-the-box)
• dspace-geoip - Project that deploys MaxMind GeoIP releases (http://sourceforge.net/projects/geoip/) to Maven Central for DSpace (so DSpace can use it as a dependency & include it out-of-the-box)

...