Versions Compared

Old Version 1

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version Current

changes.mady.by.user Tim Donohue

Saved on

Key

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

Table of Contents

Date

Note

This meeting is one hour later for anyone who has entered daylight saving time (e.g. most of USA). 15:00UTC is now 11:00am EDT.

Since Europe enters daylight saving time this weekend, our meeting on March 30 will switch to 14:00UTC (10:00am EDT)

Date

 from 15:00-16:00 UTC

...

Info
title7.6 Release Plan (TBD - NOT FINALIZED)

Release Schedule:

  • TBD Friday, April 7 (Donated Feature Notification Deadline): Any community members who wish to donate a feature to this release must notify Tim Donohue by this date (either via email, Slack or GitHub). The DSpace 7 team will then provide feedback on whether it will be possible to include this feature in the release (based on team member availability and the size of the feature).  Early notifications are more likely to get included in the release.
  • TBD Friday, Apr 28 (Feature PR Creation Deadline):PRs should be created by this date if they are to be reviewed in time for the release.  Please note there is no guarantee that a PR will be included if it is created by this date. Larger PRs are recommended to be created earlier, as that makes it more likely they can be reviewed in time for inclusion. (Smaller bug fixes are welcome anytime)
  • TBD Friday, May 12 (Feature PR Review/Test Deadline): All code reviewers or testers should submit their feedback by this date. Code reviews must be constructive in nature, with resolution suggestions. Any code reviews submitted AFTER this date will be considered non-blocking reviews. NOTE: Larger PRs or donated PRs may have their own deadlines established for PR creation, review and merger.This deadline only applies for PRs with no other deadline established.
  • TBD Friday, May 19 (Bug PR Creation Deadline):Bug fix PRs are still acceptable after this date if they are very high priority.  However, any submitted after this date will likely need to have pre-assigned reviewers in order to ensure the review can be completed before the PR Merge Deadline.
  • TBD Friday May 26 (PR Merge Deadline): All PRs should be merged by this date.  (Note: bug fixes can still get in after this deadline, as long as they are small or important)
  • Week of TBD May 29-June 2 (Documentation & Release Week):  Any merged PRs which don't have minimal documentation (how to enable / configure) MUST have documentation created this week. Later in this week (around Thurs) will be the release.
  • TBD Monday, June 5: Public Release Announcement. 7.6 will be announced/released by this date.

Ongoing/Weekly tasks:

...

  • (30 mins) General Discussion Topics
    1. Planning for 7.6
      1. Review the 7.6 board
        1. Steering has voted to fund the following tasks for 7.6.  Need volunteers to claim.
          1. Upgrade to Angular 15 (estimated at 60hrs): https://github.com/DSpace/dspace-angular/issues/2043
          2. Support "Primary Bitstream" concept (estimated at 40-60hrs): https://github.com/DSpace/DSpace/issues/3349 and https://github.com/DSpace/dspace-angular/issues/1578
          Determine which tickets need to be brought back to Steering for possible funding (see "needs funding" label)
        2. Determine which tickets in "In Progress" column are still being worked on for 7.6.  Do any of these need to be taken off the 7.6 board and moved to 8.0?
        3. 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
          2. Administer Workflow Actions no longer work: https://github.com/DSpace/dspace-angular/issues/2118
      2. Finalize Timeline for 7.6:  Looking at an early June release (possibly announce on Monday, June 5?), unless we feel it can be moved forward into May.
        1. Tim will update release schedule above once we set a goal.
      3. General rule for 7.6:  New features are welcome if they used to exist in 6.x.  Everything else must be a fix that would normally be acceptable in a "bug fix only" release.
        1. 7.6 is a "transition" release, where we are transitioning back to our release numbering scheme
      4. Releases after 7.6:  Later releases will be bug-fix only.
        1. Andrea Bollini (4Science) and Lieven Droogmans suggest to switch to a 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. With 8.0 however, we would move back to our existing release numbering scheme.  Bug fix releases would be numbered 8.1, 8.2, 8.3, etc.
    2. (NO UPDATES) 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 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. (Future Topic) Lyrasis' new CEO has asked Tim Donohue to investigate what it would take to implement OCFL-based storage (or similar preservation-friendly storage) for DSpace (v8 or later)
      1. Early brainstorm is to likely keep DSpace's existing database & Solr usage as-is.
      2. However, migrate from current "[dspace]/assetstore" to an OCFL storage structure. 
        1. OCFL storage would contain both the content file(s) (PDF, etc) and a metadata representation (exported/synced from database). The metadata representation might be similar to our existing DSpace AIP Format.
        2. Tools would need to verify/validate that data in OCFL storage "matches" with what is in the database (similar to a Checksum Checker, but more specific to OCFL storage)
      3. If anyone is interested in brainstorming this idea further, get in touch with Tim.
    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

...