Versions Compared

Key

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

...

  • (30 mins) General Discussion Topics
    1. Finalizing the 7.5 release
      1. DRAFT of Release Notes: Release Notes#7.5ReleaseNotes 
        1. Please review for correctness.  Let me know if you donated something and were NOT attributed.  Please also make sure all "Donated by" attributions are correct.
      2. Plan is to cut the release today (Thurs, Feb 16). Any objections?
      3. Last minute bug
        1. No option appears for Bundle when the user is uploading a bitstream: https://github.com/DSpace/dspace-angular/issues/2101 (Partial fix?: https://github.com/DSpace/dspace-angular/pull/2102)
    2. Demo Site maintenance (https://demo7.dspace.org/ and https://api7.dspace.org/server/)?  
      1. UPDATE: 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 March or 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 ?
    3. (TIME PERMITTING) Beginning to think about 7.6 & "7.x nearing feature completion"
      1. Next week, DSpace Steering will discuss which outstanding features to prioritize for 7.6 from the Tier List: DSpace Release 7.0 Status#Tier3:MediumPriority  HIGHEST PRIORITY will be for features which used to exist in 6.x but no longer exist in 7.x. (However, it is possible some low priority features may be removed from the 7.x list & rescheduled for 8.0 instead)
      2. Brainstorms of other tasks we feel are necessary to accomplish with 7.6
        1. E.g. any additional performance improvements or similar, per DSpace 7 UI Optimization Analysis?
    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.5 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

...