6.5 release notes #11067
6.5 release notes #11067
Conversation
pdurbin
added
Size: 10
| - UX improvements, especially Preview URLs | ||
| - increased harvesting flexibility | ||
| - performance gains | ||
| - a security vulnerability addressed |
There was a problem hiding this comment.
I don't think we ever put out a security announcement. We probably should. See https://guides.dataverse.org/en/6.4/developers/security.html#sending-security-notices
This is the bug that was fixed: https://github.com/IQSS/dataverse-security/issues/98 . Should we link to it from the release notes for the people who have access?
There was a problem hiding this comment.
Some discussion here: https://iqss.slack.com/archives/C03R1E7T4KA/p1733507189175279
We decided to link to the security issue.
Co-authored-by: Omer Fahim <[email protected]>
Co-authored-by: Omer Fahim <[email protected]>
|
|
||
| ## Settings Added | ||
|
|
||
| - `:GlobusBatchLookupSize` |
There was a problem hiding this comment.
Do we need a description/explanation here?
There was a problem hiding this comment.
We've always had a "settings added" section and I think it's helpful to the sysadmins to always have this list to go to, even if it's short this time.
|
|
||
| Replace schema.xml | ||
|
|
||
| Please note that the path to Solr may differ than the example below. |
There was a problem hiding this comment.
Should we note the directory for developers deploying containers?
There was a problem hiding this comment.
Hmm, the main audience is not developers so I don't think so. Maybe we should sent an email to the dev list?
|
Looks good overall. I left a couple of comments/questions |
Co-authored-by: Omer Fahim <[email protected]>
Co-authored-by: Omer Fahim <[email protected]>
Co-authored-by: Omer Fahim <[email protected]>
There was a problem hiding this comment.
Looks good. The one nit I have is that using the api/admin/index call (step 8) is not actually the one we talk about as reindex in place in the guides. That refers to deleting the time stamps for indexing and then calling continue. We could ignore this, just drop the 'reindex-in-place' phrase, or show the other calls. I'm not sure which is best - if the server is restarted before the /api/admin/index call completes, is there a way to restart like there is if you clear the index or delete the timestamps?
|
reviewed and proof-read. Merging PR |
What this PR does / why we need it:
Release notes, as usual. Preview at https://github.com/IQSS/dataverse/blob/10952-release-notes/doc/release-notes/6.5-release-notes.md
Which issue(s) this PR closes:
Special notes for your reviewer:
I'll leave some comments inline.
Suggestions on how to test this:
Go through the upgrade steps on demo. Here's the issue for that: