Page tree
Skip to end of metadata
Go to start of metadata


 from 14:00-15:00 UTC

Location: (Meeting ID: 502 527 3040).  Passcode: dspace

Testathon Sprint : Ongoing


  • (BEFORE MEETING IN #dev-sprint) Developer Stand Up - Developers give brief updates on their effort (or their team's effort).

    • Update/see "Current Work" section below based on your status. Please feel free to update prior to meeting.
    • Please highlight any new work (needing reviews/testing), any blockers (for you), and any discussion topics you may have.
  • (30 mins) General Discussion Topics
    1. Beta 5 Release Schedule & Testathon Dates (APPROVED by Steering)
      1. Beta 5 Release Date: TODAY (April 15)
      2. Testathon (3 weeks): April 19 - May 7  (See DSpace Release 7.0 Testathon Page)
    2. Status update on Testathon Demo Sites
      1. Updated Demo Content available at
        1. should be updated with this data prior to Testathon.  Should we have a way to reset passwords if testers change them?
        2. Accessibility site (for Deque) should be updated to Beta 5 code once released
    3. Our Dev meetings during Testathon will involve two boards:   
      1. 7.0 Project Board - These are tickets we are planning to complete prior to 7.0 Final.  Tickets here can be worked on during Testathon.
        1. In each meeting, we will review this board & continue to estimate tickets, assign to work on, review/test, etc. Any tickets merged will be deployed immediately to the Testathon demo servers.
        2. Once Testathon is completed, based on estimated work on 7.0 Board & in consultation with Steerring, we'll set a goal/date for 7.0 final.  This may involve re-prioritizing tickets on the 7.0 board as necessary.
      2. Backlog Board - New bugs/issues reported during Testathon will appear on this board (in "Triage" column).
        1. Tim Donohue can take lead on Triage (but others welcome). As necessary, he will pull in developer(s) who worked on that feature to do a quick estimate, prioritization & (as necessary) assign the work.
        2. Once triaged, ticket will move to 7.0, 7.1 or 7.2 project board based on priority.  Tickets may also move between 7.0/7.1/7.2 boards if priority changes (based on additional feedback, etc.)
        3. During our weekly meetings, we'll glance at the "Triage" column for newly reported bugs & help move them along if needed.
    4. Updating 7.0 Documentation (prior to / during Testathon)
        1. Installation Guide for Angular UI. Currently no Production-level instructions at Installing DSpace
        2. Configuration Reference updates (Tim has been working on little by little)
        3. See also, tickets at
  • (30 mins) Planning for next week


7.0 Release Goals

These resources define the prioritization and general schedule we are working towards

Current Work

Project Board

DSpace 7.0 Beta 5 Project Board:

To quickly find PRs assigned to you for review, visit  (This is also available in the GitHub header under "Pull Requests → Review Requests"

Security / Performance Tests

Brainstorming options for security testing & performance testing.  How do we want to handle both of these prior to 7.0 final?

  1. Security Review/Scanning of pre-7.0:  See DSpace 7 Security Analysis 
  2. Performance testing of pre-7.0: See DSpace 7 Performance Analysis

Delayed / Needs Discussion

  1. Finalize / approve the initial list of all authorization features which we should implement for the /api/authz/features REST endpoint.  This list of features should be limited to only features which are required to enable/disable User Interface functionality. (In other words, we can always add more features in the future.  We just need to approve the list necessary for 7.0)
      1. Review current spreadsheet (from Andrea Bollini (4Science) ) : 
        1. Art Lowel (Atmire) : I don't see any immediate issues with the current set of features, but I would prefer a consistent naming scheme. I'd use canDoSomething for everything
        2. Tim Donohue added possible renames of these features based on Art's idea (see cell comments in spreadsheet).  I like the "can[DoSomething]" naming scheme as well.
  2. (REST Contract) Edit Homepage News:
    1. Delayed. General agreement (in meeting on March 21, 2019) that storing HTML in metadata fields is not really ideal behavior.  Metadata (from a librarian standpoint) tends to be free of format-related markup (as that allows for easier sharing, understanding of metadata.  Currently Community & Collection homepage information is HTML-based and is stored in metadata that is appropriate for a minor subset of information (like the title) but it is better to move large/rich text to bitstreams.  
    2. Proposal here is to consider storing HTML-based markup (for Site, Community & Collection homepages) in Bitstream(s) associated with the object in question.  May allow for more CMS-lite behavior in the future
    3. Timeline for this is uncertain.  Possibly in 7 or 8. May depend on how/whether it can be scoped.