5.10 release notes #8464
5.10 release notes #8464
Conversation
planned for the next release, at least
Added a few extra words about the schema and the fact that an updated schema is needed in order to be able to index any datasets with multiple collMode fields, which is now possible per the metadata block update.
| - Dataset editors can now deselect a guestbook. (Issue #2257, PR #8403) | ||
| - Administrators with a large `actionlogrecord` table can read docs on archiving and then trimming it. (Issue #5916, PR #8292) | ||
| - Administrators can list locks across all datasets. (PR #8445) | ||
| - Administrators can run a version of Solr that doesn't include a version of log4j2 with serious known vulnerabilities. We trust that you have patched the version of Solr you are running now following the instructions that were sent out. An upgrade to the latest version is recommended for extra peace of mind. (PR #8415) |
There was a problem hiding this comment.
I'm not sure what normal protocol is for ordering issues, but I'd put them in order of significance since people read from the beginning and maybe don't go thru the full list, so getting them aware of the most important issues by putting them at the top of the list probably can be helpful. It seems that log4j fixes and multi-license are the most significant.
There was a problem hiding this comment.
@lenwiz I struggled a lot with how to talk about log4j. Perhaps we should have a separate section about security updates? There is an order for these bullets but it may not be the most obvious. Users are first, then curators, then administrators, then sysadmins. Basically, I'm trying to put the stuff at the top that affects the most people. Sysadmins, of which there are few, are probably the only ones who know about log4j. So I put it last with the sysadmin stuff.
@landreev I see you gave this comment a 👍 so please feel free to join in. 😄 I'm in no rush to click "resolve conversation".
Bottom line, I'm inclined to leave it alone but I'm open to reordering, even if it goes against by "most people" logic above. 😄
What this PR does / why we need it:
Adds 5.10 release notes.
Which issue(s) this PR closes:
Special notes for your reviewer:
The original 7440-multilicense.md file had lots of details at the end, after all the Payara "deploy" commands and such but because they need to be understood and executed (if needed) before deployment, I moved them up.
Suggestions on how to test this:
I didn't test the SQL commands. I assume they work. I guess one could run through an upgrade? Really I just did the normal editing of text according to our process.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No.
Is there a release notes update needed for this change?:
This IS a release note. 😄
Additional documentation:
None.