Policy Question: Do we have an End-of-Life, End-of-Service policy for Harvesting feature?

[mreekie]

It does not appear that we have a policy governing interoperability features. Specifically for this issue: Harvesting.
If we are at a point where it is feasible to make a policy let's do it.

Context:

• It's clear that we can't support all versions.
• Can we reasonably expect that our customers always upgrade?
• This issue was triggered from a discussion around a customer issue.
  • see: Dataverse installation using Dataverse v5.3 is unable to harvest datasets from Dataverse installation running Dataverse v5.12 dataverse#9197

Acceptance Criteria:

• Creation of the policy
• Policy documented and made available a page around the harvesting feature that documents our policy towards supporting issues with harvesting for older versions of the software.
• Publish the result out to customers.

[mreekie]

discussion with Julian.

• This is not something impacting the harvard dataverse installation.
• It's important enough that I'd like it considered.
• Putting this in the "new" queue for global backlog

[mreekie]

Grooming:

This issue was in the New or No Status columns on the Dataverse Global Backlog Board.
Those columns have been removed.
This issue has been removed from the board

This is NOT a reflection of the priority of these issues.
However, as we have worked on the grooming process, it became clear that these issues which are in columns that are not stewarded will likely not get prioritized or sized.

To get this item onto the Dataverse Global Backlog Board, please reach out to one of the Stewards on the board.
You can also reach out to @mreekie and I can connect you with the steward of the appropriate queue

[cmbz]

2024/03/18

• As per our harvesting meeting on 2024/03/12, @scolapasta will "Modify policy issue to reflect discussion"

[cmbz]

@scolapasta Reminder, you said you'd complete by first week in October.