Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • (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: Friday, April 9 or Monday, April 12 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 https://github.com/DSpace-Labs/AIP-Files/releases/tag/demo-entities-data
        1. https://api7.dspace.org should be updated with this data prior to Testathon.  Should we have a way to reset passwords if testers change them?
        2. Need a second demo Accessibility site (for Accessibility Analysis by Deque. Should also be initialized with this content. 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 will perform initial triage 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 https://github.com/orgs/DSpace/projects/5?card_filter_query=label%3Adocumentation
  • (30 mins) Planning for next week

...