This repository was archived by the owner on May 1, 2025. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah sorry, I didn't mean for REP-5495 to generate a downstream DOCSP ticket. I think we should just document REP-5495's changes on the release notes based on the google doc.
I don't think we should include this in our general docs because it exposes too much information about our logs. We say that our logs are not versioned and can change at any time here. I think we can close this ticket as won't do.
@zhenxuanjameszhang do you have thoughts on this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think currently something is broken that if we select manual to add release notes, a DOCSP ticket will still be auto generated. I have noted that on the release process to improve.
I trust your judgement on this.