Versions Compared

Key

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

...

Info
title7.3 Release Plan

Release Schedule (TENTATIVE, may need revising based on OR2022 plans):

  • Thursday, Apr 28 (PR Creation Deadline): All new feature (or larger) PRs should be created by this date. (Smaller bug fixes are welcome anytime)
  • Thursday, May 19 (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. This means feedback received after Jan 20 is optional to address (unless the team or PR developer decides it is required).
  • Friday, May 27 (PR Merge Deadline): All new feature PRs should be merged by this date. (Bug fixes can still get in, as long as they are small or important)
  • Week of May 30: Internal / Early release goal. If possible, we'd like to release 7.3 in late May or first week of June.
  • Monday, June 6: Public Release Deadline. 7.3 must be announced/released by this date.

Ongoing/Weekly tasks:

Likely 7.3 major new features (tentative):

  1. (TIER 1) (Admin) Ability to preview Batch Metadata changes during import of CSV, similar to 6.x.  In 7.x, it is possible to import a CSV from the Admin Toolbar, but you are not shown a preview of pending changes. (UI ticket #782 , REST ticket #2849)
  2. (TIER 1) (Workflow) Preview an item during workflow approval to allow for easier accepting/rejecting, similar to 6.x (UI ticket #772)
  3. (TIER 1) (Admin) Ability to export metadata (to CSV) from search results, similar to 6.x. (REST Ticket #3129 )
  4. (TIER 2) (
Integrations
  1. NEW) Advanced ORCID integration port from DSpace-CRIS to DSpace (Ticket #8157)
  2. (
Integrations
  1. TIER 2) (NEW) Migrate additional "Live-Import" sources from DSpace-CRIS to DSpace: (Ticket #3359)
  2. (TIER 2) (NEW) Versioning support for Entities: (UI ticket #1312, REST ticket #7937)
  3. (TIER 2) (General) Support for hierarchical controlled vocabularies in Search interfaces, similar to 6.x  (UI ticket #815, REST ticket #2870)
  4. (TIER 2) (Submission) SHERPA/RoMEO integration in Submission UI, similar to 6.x (UI ticket #769, REST ticket #2840)
  5. (TIER 2) (Admin) Administrative Control Panel (similar to 6.x XMLUI) (UI ticket #801, REST ticket #2877) 
  6. (TIER 2) (NEW) Signposting support, aligning with recommendations from the COAR Next Generation Repositories Report (UI ticket #811, REST ticket #2881)
  7. Upgrading to Angular 12 or 13 (UI ticket #1432), and UI performance improvements (e.g. UI ticket #741 and UI ticket #1357)

Agenda

  • (30 mins) General Discussion Topics
    1. Open Repositories 2022 (June 6-9 in Denver). Who is planning to attend? What would we want to plan for DSpace 7?
      1. DSpace 7.2/7.3 workshop: Leaning towards holding an online workshop/webinar instead of a workshop at OR2022. 
      2. DSpace 7.2/7.3 talks: Team noted it would be best to have at least one DSpace 7 talk at OR2022 in order to provide an update to the OR community.  Additional talks might be moved online perhaps alongside the online workshop? 
    2. Review tentative 7.3 Release Schedule above. This is based on a new 4-month release window, but could conflict with OR2022 plans.
    3. Any assigned 7.3 work needing early discussion?
      1. Result from the OpenAIRE ELD project https://www.openaire.eu/openaire-eld-enrich-local-data-via-the-openaire-graph - 4Science is going to update this work to be considered in 7.3
      2.  Early design of Administrative Control Panel: https://github.com/DSpace/DSpace/issues/2877#issuecomment-1036325871
        1. Plan to use Spring Boot Actuator endpoints: https://docs.spring.io/spring-boot/docs/current/reference/html/actuator.html
    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.3 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.

...