Skip to content

Commit 593046b

Browse files
author
Karl Heinz Struggl
committed
replicates Android docs for other mobile sdks
1 parent 3a036eb commit 593046b

File tree

3 files changed

+123
-0
lines changed

3 files changed

+123
-0
lines changed
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
title: Mobile SDK Releases
3+
description: "Learn about Sentry's release channels for Mobile SDK updates."
4+
sidebar_order: 7000
5+
---
6+
7+
The Apple SDK uses the following channels to release SDK updates:
8+
9+
## `Pre-release`
10+
11+
Pre-releases (alpha, beta, RC,…) are for larger and potentially more impactful changes, such as new features or major versions.
12+
13+
## `Latest`
14+
15+
We continuously release major/minor/hotfix versions from the `main` branch. These releases go through all our internal quality gates and are very safe to use. They're intended to be the default for most teams.
16+
17+
## `Stable`
18+
19+
Releases are promoted from `Latest` to `Stable` when they've been used in the field for some time and at some scale. The length of time a release has been out, the level of adoption, and other quality and stability metrics are all considered before a release is deemed `Stable`. These types of releases will have a `Stable` label on the <Link to="https://github.com/getsentry/sentry-cocoa/releases/">releases page</Link>.
20+
21+
## FAQ
22+
23+
### Where can I find the latest stable release for any given SDK?
24+
25+
On the <Link to="https://github.com/getsentry/sentry-cocoa/releases/">releases page</Link> of the SDK's GitHub repo. Stable releases will have the `Stable` label in the name of the release. You can also use the search box in the top right to search for the newest releases.
26+
27+
### Does this mean the release channels are not stable?
28+
29+
No. Stability and performance are the top priorities for every release. The `Stable` release status means that the release has been tested and proven to work in the wild and at scale.
30+
31+
### How often do we mark SDKs as stable?
32+
33+
The stable release cycle depends on a number of factors and can vary, but the target cadence is to provide stable releases roughly every month.
34+
35+
### Should I only use stable releases?
36+
37+
We leave this decision up to you. Stable releases have been tested in the field and at significant scale. They are intended for a dependable and consistent experience. Please note that the `Stable` release channel will get our newest features later than other releases.
38+
39+
### How does this relate to the stability of a feature?
40+
41+
A `Stable` release status doesn't guarantee the stability of an SDK feature or product feature. A new feature that's still experimental might be part of a stable SDK release. Any experimental features will be clearly marked and offered as an opt-in.
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
title: Mobile SDK Releases
3+
description: "Learn about Sentry's release channels for Mobile SDK updates."
4+
sidebar_order: 7000
5+
---
6+
7+
The Flutter SDK uses the following channels to release SDK updates:
8+
9+
## `Pre-release`
10+
11+
Pre-releases (alpha, beta, RC,…) are for larger and potentially more impactful changes, such as new features or major versions.
12+
13+
## `Latest`
14+
15+
We continuously release major/minor/hotfix versions from the `main` branch. These releases go through all our internal quality gates and are very safe to use. They're intended to be the default for most teams.
16+
17+
## `Stable`
18+
19+
Releases are promoted from `Latest` to `Stable` when they've been used in the field for some time and at some scale. The length of time a release has been out, the level of adoption, and other quality and stability metrics are all considered before a release is deemed `Stable`. These types of releases will have a `Stable` label on the <Link to="https://github.com/getsentry/sentry-dart/releases/">releases page</Link>.
20+
21+
## FAQ
22+
23+
### Where can I find the latest stable release for any given SDK?
24+
25+
On the <Link to="https://github.com/getsentry/sentry-dart/releases/">releases page</Link> of the SDK's GitHub repo. Stable releases will have the `Stable` label in the name of the release. You can also use the search box in the top right to search for the newest releases.
26+
27+
### Does this mean the release channels are not stable?
28+
29+
No. Stability and performance are the top priorities for every release. The `Stable` release status means that the release has been tested and proven to work in the wild and at scale.
30+
31+
### How often do we mark SDKs as stable?
32+
33+
The stable release cycle depends on a number of factors and can vary, but the target cadence is to provide stable releases roughly every month.
34+
35+
### Should I only use stable releases?
36+
37+
We leave this decision up to you. Stable releases have been tested in the field and at significant scale. They are intended for a dependable and consistent experience. Please note that the `Stable` release channel will get our newest features later than other releases.
38+
39+
### How does this relate to the stability of a feature?
40+
41+
A `Stable` release status doesn't guarantee the stability of an SDK feature or product feature. A new feature that's still experimental might be part of a stable SDK release. Any experimental features will be clearly marked and offered as an opt-in.
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
title: Mobile SDK Releases
3+
description: "Learn about Sentry's release channels for Mobile SDK updates."
4+
sidebar_order: 7000
5+
---
6+
7+
The React Native SDK uses the following channels to release SDK updates:
8+
9+
## `Pre-release`
10+
11+
Pre-releases (alpha, beta, RC,…) are for larger and potentially more impactful changes, such as new features or major versions.
12+
13+
## `Latest`
14+
15+
We continuously release major/minor/hotfix versions from the `main` branch. These releases go through all our internal quality gates and are very safe to use. They're intended to be the default for most teams.
16+
17+
## `Stable`
18+
19+
Releases are promoted from `Latest` to `Stable` when they've been used in the field for some time and at some scale. The length of time a release has been out, the level of adoption, and other quality and stability metrics are all considered before a release is deemed `Stable`. These types of releases will have a `Stable` label on the <Link to="https://github.com/getsentry/sentry-react-native/releases/">releases page</Link>.
20+
21+
## FAQ
22+
23+
### Where can I find the latest stable release for any given SDK?
24+
25+
On the <Link to="https://github.com/getsentry/sentry-react-native/releases/">releases page</Link> of the SDK's GitHub repo. Stable releases will have the `Stable` label in the name of the release. You can also use the search box in the top right to search for the newest releases.
26+
27+
### Does this mean the release channels are not stable?
28+
29+
No. Stability and performance are the top priorities for every release. The `Stable` release status means that the release has been tested and proven to work in the wild and at scale.
30+
31+
### How often do we mark SDKs as stable?
32+
33+
The stable release cycle depends on a number of factors and can vary, but the target cadence is to provide stable releases roughly every month.
34+
35+
### Should I only use stable releases?
36+
37+
We leave this decision up to you. Stable releases have been tested in the field and at significant scale. They are intended for a dependable and consistent experience. Please note that the `Stable` release channel will get our newest features later than other releases.
38+
39+
### How does this relate to the stability of a feature?
40+
41+
A `Stable` release status doesn't guarantee the stability of an SDK feature or product feature. A new feature that's still experimental might be part of a stable SDK release. Any experimental features will be clearly marked and offered as an opt-in.

0 commit comments

Comments
 (0)