Skip to content
This repository has been archived by the owner on Oct 30, 2024. It is now read-only.

clarify preview release #854

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Conversation

shorgi
Copy link
Contributor

@shorgi shorgi commented May 20, 2024

No description provided.

Copy link

netlify bot commented May 20, 2024

Deploy Preview for apollo-monodocs failed.

Name Link
🔨 Latest commit d53bb21
🔍 Latest deploy log https://app.netlify.com/sites/apollo-monodocs/deploys/664bc31ed29b120008021d03

A preview might still contain bugs or undergo iteration. You're encouraged to try previews in test environments to familiarize yourself with upcoming functionality before it reaches [general availability](#general-availability).
Previews aren't officially supported with any SLA, and breaking API changes are possible between incremental versions of a preview.

We encourage you to provide your feedback about functionality and issues you encounter when trying previews in your development and test environments. We might release multiple previews before the functionality reaches [general availability](#general-availability).
Copy link
Contributor

Choose a reason for hiding this comment

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

This verbiage suggests previews should only be used in dev/test environments. I'm not sure if we want to limit them to this?

Suggested change
We encourage you to provide your feedback about functionality and issues you encounter when trying previews in your development and test environments. We might release multiple previews before the functionality reaches [general availability](#general-availability).
We encourage you to provide your feedback about functionality and issues you encounter when trying preview features. We might release multiple previews before the functionality reaches [general availability](#general-availability).

@@ -53,4 +55,4 @@ Products, features, and open-source releases that reach end-of-life are no longe

End-of-life releases published to a package registry aren't removed from that registry. This means you can still install end-of-life versions past the end-of-life date (though Apollo strongly recommends against this).

Do not run end-of-life open-source releases in production. Upgrade to the latest generally available release as soon as possible to ensure you continue receiving security patches, bug fixes, new features, and compatibility with GraphOS features.
**Do not run end-of-life open-source releases in production**. Upgrade to the latest generally available release as soon as possible to ensure you continue receiving security patches, bug fixes, new features, and compatibility with GraphOS features.
Copy link
Contributor

Choose a reason for hiding this comment

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

Per Stellar's feedback, we should limit bolding for UI elements and italics for new features. Not sure if this needs emphasis.

Suggested change
**Do not run end-of-life open-source releases in production**. Upgrade to the latest generally available release as soon as possible to ensure you continue receiving security patches, bug fixes, new features, and compatibility with GraphOS features.
Do not run end-of-life open-source releases in production. Upgrade to the latest generally available release as soon as possible to ensure you continue receiving security patches, bug fixes, new features, and compatibility with GraphOS features.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants