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.

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

DOC-737 K8s 6.0.20-4 release notes #1398

Merged
merged 5 commits into from
Jun 14, 2021
Merged

DOC-737 K8s 6.0.20-4 release notes #1398

merged 5 commits into from
Jun 14, 2021

Conversation

kaitlynmichael
Copy link
Contributor

@kaitlynmichael kaitlynmichael self-assigned this Jun 10, 2021
@kaitlynmichael kaitlynmichael changed the title Doc 737 K8s 6.0.20-4 release notes DOC-737 K8s 6.0.20-4 release notes Jun 10, 2021
Copy link
Contributor

@laurentdroin laurentdroin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're missing the following, is it on purpose?

Compatibility Notes
OpenShift 4.7 and Rancher/kOps 1.20 are now supported
OpenShift 4.1, 4.2, 4.3 (previously deprecated) are no longer supported
GKE K8s version 1.14 (previously deprecated) is no longer supported
kOps (upstream K8s) 1.13, 1.14 (previously deprecated) are no longer supported

Deprecation notice
OpenShift 4.4 (no longer supported by Red Hat) is deprecated
GKE K8s versions 1.15, 1.16 (no longer supported by Google) are deprecated
kOps (upstream K8s) 1.15 is deprecated

@laurentdroin
Copy link
Contributor

Also, in order to stay consistent with the previous RN, don't we want to keep the title for each known limitation? The titles seem to have been stripped from the source github page.

@kaitlynmichael
Copy link
Contributor Author

kaitlynmichael commented Jun 11, 2021

I understand that we want to be consistent but I didn't think the Jira numbers and titles were adding any value on the public site. Internally, they are useful. For the public, I believe just a description of the problem is all that's necessary. If this has a significant negative impact on customers, we can include the titles and numbers.

@kaitlynmichael
Copy link
Contributor Author

We're missing the following, is it on purpose?

Good catch! It is not on purpose. I'll add those asap.

@amiramm
Copy link
Collaborator

amiramm commented Jun 14, 2021

understand that we want to be consistent but I didn't think the Jira numbers and titles were adding any value on the public site. Internally, they are useful. For the public, I believe just a description of the problem is all that's necessary. If this has a significant negative impact on customers, we can include the titles and numbers.

@kaitlynmichael we use these ticket numbers with customers and they expect to see them. Otherwise, every time we would need to refer to an issue, we would need to repeat the entire description and that's just not practical. We need to keep those, please. Thanks.

Copy link
Collaborator

@amiramm amiramm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this! please review comments/edits.

@kaitlynmichael kaitlynmichael merged commit 5314aff into master Jun 14, 2021
@kaitlynmichael kaitlynmichael deleted the DOC-737 branch June 14, 2021 18:32
slorello89 pushed a commit to slorello89/redislabs-docs that referenced this pull request Jun 15, 2021
* 6.0.20-4 release notes
* hugo error
* fix weight and relref
* compatibility and deprecation notes
* added back titles and ticket numbers, bugs and limitation
Co-authored-by: Amiram Mizne <amiramm@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants