Page History

...

• Discussion of which DSpace Summer of CodeCode2 projects are "trunk ready" (i.e. ready for DSpace 1.7 release). Two projects proposed to add to Trunk:
  • GSOC10 - Add Unit Testing to Dspace
    • Seem to have general agreement that this code should be accepted to Trunk. Although not all unit tests are completed, the framework is necessary to get into Trunk so that we can continue to build out additional unit tests, etc.
  • GSOC10 - DSpace REST API
    • Some disagreement on accepting this project immediately. Most seem in favor, but a few concerns posted.
      • grahamtriggs: "I've only briefly scanned the commits, but the code where it is getting stack traces and using it to determine if there is a loop seems rather scary, and is pointing to a flawed designed"
• How should this code be committed?
  • General agreement that Mentors should "sponsor" a student's access to Trunk. Students would essentially be given temporary commit rights to Trunk in order to merge their code in (as necessary).
    • mhwood: Could the mentor "sponsor" (or not) his student's access to trunk? "Sponsor" meaning, "I think the code is good, I think the student knows his way around the SCM, and I'll help clean up if I was mistaken."
• Voting:
  • Proposal: "All those in favor of having Pere Villega commit his "ready" Unit Testing code (with sponsorship from Stuart Lewis) to Trunk before the end of GSoC?"
    • +1 votes : 7 people
    • -1 votes : 0 people
    • 0 votes : 0 people
    • Final Results: Proposal passes – the Unit Testing code should be added to Trunk before end of GSoC.
  • No other proposals were made (ran out of time for discussion). During next week's meeting (Aug 4), we will continue discussion of whether REST project should also be added to Trunk.

...