Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DBaaS release notes for v147 and v148 #199

Merged
merged 5 commits into from
Oct 2, 2024
Merged

DBaaS release notes for v147 and v148 #199

merged 5 commits into from
Oct 2, 2024

Conversation

klasahl
Copy link
Contributor

@klasahl klasahl commented Aug 23, 2024

Added DBaaS release notes for CCX v147 and v148.

@klasahl klasahl requested a review from a team August 23, 2024 08:51
@argocd-elastx-public argocd-elastx-public bot temporarily deployed to dbaas_changelog_v147_v148 August 23, 2024 08:53 Inactive
@klasahl klasahl removed the request for review from a team September 18, 2024 11:35
@klasahl klasahl marked this pull request as ready for review October 1, 2024 08:09
@klasahl klasahl requested a review from a team October 1, 2024 08:09
@argocd-elastx-public argocd-elastx-public bot temporarily deployed to dbaas_changelog_v147_v148 October 1, 2024 08:10 Inactive
@nyxi
Copy link
Contributor

nyxi commented Oct 1, 2024

Generally speaking I think these public changelogs needs to be written in such a way that they make sense to the customers:

  • Only list significant changes/features - no one cares about a few new navigational bar icons
  • Proper descriptions, ie. what is "automated failure handling"? "Improved auto failover", what is the improvement?
  • Maybe we should stick to established terms for the "type" of change, ie. "feature", "fix", "documentation"?

@argocd-elastx-public argocd-elastx-public bot temporarily deployed to dbaas_changelog_v147_v148 October 1, 2024 09:58 Inactive
@argocd-elastx-public argocd-elastx-public bot temporarily deployed to dbaas_changelog_v147_v148 October 1, 2024 11:03 Inactive
@klasahl
Copy link
Contributor Author

klasahl commented Oct 1, 2024

I think the detail level is good, for each major release have as few sections as possible, suggestion is Introduction, Changes and Important fixes. I want to keep it short and informative and I agree that only important customer facing changes shall be adressed.

What do you think of the revised suggestion?

@klasahl klasahl merged commit afcf6fd into master Oct 2, 2024
5 checks passed
@klasahl klasahl deleted the dbaas_changelog_v147_v148 branch October 2, 2024 20:46
@klasahl klasahl restored the dbaas_changelog_v147_v148 branch October 3, 2024 06:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@nyxi nyxi nyxi approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@klasahl @nyxi