Page History

...

• (30 mins) General Discussion Topics
  1.  DSpace 7.6 ongoing development
     1. 7.6 code review process brainstorms
        
        1. Tim can continue to triage all new tickets/PRs coming in.
        2. However, additional support for code reviewing/testing will be necessary. New contributors are getting involved in bug fixes, and helping check/review there code would encourage further involvement.
        3. Ideas of how to better distribute / split up code reviews?  If everyone can claim a few, it'll decrease PR backlog quickly.
     2. Very High priority bugs located in 7.5:
        1. Submission form "Type" dropdown changes values when pressing Enter: https://github.com/DSpace/dspace-angular/issues/2145  Might be related to Safari browser dropdown issues: https://github.com/DSpace/dspace-angular/issues/2124
     3. Releases after 7.6:  Later releases will be bug-fix only.
        1. Tim will bring to Steering the suggestion to switch post-7.6 release numbering to 7.6.1, 7.6.2, 7.6.3 (for eventual bug fix release). This clarifies that 7.6 is the final feature release, and that every later release is a minor upgrade.
  2. (NEXT WEEK) On April 13, Pierre Lasou and Jeff Morin from U of Laval will join to discuss their work on porting REST API Reporting capabilities to v7
     1. Ticket: https://github.com/DSpace/DSpace/issues/7641
     2. Frontend PR: https://github.com/DSpace/dspace-angular/pull/2163
     3.  Backend PR: https://github.com/DSpace/DSpace/pull/8598 and Contract PR: https://github.com/DSpace/RestContract/pull/202
  3. (No Major Updates this week) Demo Site maintenance (https://demo7.dspace.org/ and https://api7.dspace.org/server/)?  
     1. LYRASIS is still working on this, but some restructuring of plans has had to occur because of internal deadline changes.  Likely not to be completed until late April.
     2. In the meantime, can we ensure that it is still possible to send updates to both the frontend & backend per instructions at Updating DSpace 7 Demo Sites 
  4. (Other topics?)
• (30 mins) Planning for next week
  • Review the Backlog Board - Are there any tickets here stuck in the "Triage" column?  We'd like to keep this column as small as possible.
  • Review the 7.6 Project Board - Assign tickets to developers & assign PRs to reviewers.
    • Paid (by DSpace project) developers must keep in mind priority. If new "high" or "medium" priority tickets come in, developers should move effort off of "low" priority tasks.
    • Volunteer developers are allowed to work on tickets regardless of priority, but ideally will review code in priority order

...