Conversation
| - `service payara stop` | ||
| - `service payara start` | ||
|
|
||
| 6\. Kick off full reindex |
There was a problem hiding this comment.
Dumb Don question: why are we re-indexing?
There was a problem hiding this comment.
@donsizemore - this was the note that I had:
A full re-index is needed to update the facets, as well as optionally running the "redetect file type" API on existing GeoJSON files.
There was a problem hiding this comment.
@donsizemore I'll close this out for now but let me know if there are other questions
There was a problem hiding this comment.
Ok, so it was from the GeoJSON mime type PR - but there’s zero reason to force it on everybody.
It sounds like it should be part of the "Additional Release Steps". "Step 1. - if you have any GeoJSON files misidentified as "type unknown", re-detect them following ... and then run full re-index, to update the type facets, etc."
pdurbin
left a comment
pdurbin
left a comment
There was a problem hiding this comment.
Looks good. I left a couple minor comments.
|
Thanks @pdurbin @donsizemore for the feedback! @qqmyers I added the analytics fix information. Feel free to edit/comment. |
|
|
||
| Please note that the Auxiliary files feature is experimental and is designed to support integration with tools from the [OpenDP Project](https://opendp.org). If the API endpoints are not needed they can be blocked. | ||
|
|
||
| ## Major Use Cases and Infrastructure Enhancements |
There was a problem hiding this comment.
I don't want to make or request changes at the very last moment that are essentially about changing our process/the established structure of these notes. But this just feels wrong, to have long, verbose descriptions of some new features, under "Release Highlits"; but then follow up with brief, concise mentions of the same features in the "Major use cases" section...
It should really be the other way around; a brief, skinny list first; then the verbose section - ?
Maybe even: 1) skinny section; 2) upgrade instruction; and only then, "if you're still reading" - the detailed descriptions for those few who have the attention span for such things - ?
(once again, I don't want to change this note, for this release)
landreev
left a comment
landreev
left a comment
There was a problem hiding this comment.
Aside from the few suggested edits, I'm happy with it.
We do need to consider changing the format of these notes, or at least rearranging the order in which we present the information, to make them more readable.
Maybe start with providing a link up top, "skip directly to the upgrade instructions ..."
6 participants
What this PR does / why we need it:
The release notes for 5.9!
Which issue(s) this PR closes:
Closes #8270
Special notes for your reviewer:
Suggestions on how to test this:
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation: