OpsCenter 6.8.31 Release #123
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
msmygit
reviewed
Nov 29, 2023
szymon-miezal
approved these changes
Nov 29, 2023
There was a problem hiding this comment.
Overall it looks good but I have a question:
are OpsC release notes reviewed by docs team the same way it's done for DSE?
The reason I ask is because I see some inconsistencies like using past and present tenses in different notes. Not like it's a major problem but I wanted to start the discussion, maybe we would like to use unified guidelines for DSE and OpsC.
|
@szymon-miezal Our checklist did specify who to get the review from. I'm not sure if it use to say to get it from the docs team. I like the idea of them doing it and will update the template to reflect that in the future. How do you reach out to them? Is there a specific person or is there a channel you ask in? |
Co-authored-by: Madhavan <msmygit@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release Notes Automation
If you name your pull-request as "Product x.y.z Release ...", after merging the
PR, a GitHub Action will automatically create a product version tag "product-x.y.z".
Supported product names are:
Version supports 3 sets or 4 sets of digits.