Release Policy: Update docs and screenshots #2679
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
myarmolinsky
force-pushed
the
update-release-policy-docs
branch
from
158c570
to
97ba723
Compare
vipulgupta2048
requested changes
Apr 23, 2023
| <img src="/img/common/release-policy/mNCaLF8.gif" width="100%" alt="Pin fleet to release"> | ||
| You can also pin a fleet to a release via the CLI as follows: | ||
| - Pin to a specific release: `balena fleet pin myorg/myfleet 91165e5` | ||
| - Track latest: `balena fleet track-latest myorg/myfleet` | ||
|
|
||
| ## Pin device to a release | ||
|
|
||
| As well as pinning a fleet to a specific release, you may pin individual devices to a specific release. By default, all devices track the fleet release. However, you may wish to run a different release on select devices, for example, a development device or when performing a [canary deployment][canary]. |
There was a problem hiding this comment.
Suggested change
| As well as pinning a fleet to a specific release, you may pin individual devices to a specific release. By default, all devices track the fleet release. However, you may wish to run a different release on select devices, for example, a development device or when performing a [canary deployment][canary]. | |
| Same as pinning a fleet to a specific release, you can pin individual devices to a specific release. By default, all devices track the fleet release. However, you may wish to run a different release on select devices, for example, a development device or when performing a [canary deployment][canary]. |
There was a problem hiding this comment.
Same isn't better semantically IMO, but I'll admin that As well is a bit odd... Arguably we really don't need that first sentence at all, right? It's implied by the existence of this doc section, isn't it?
There was a problem hiding this comment.
True that. Less is more.
Comment on lines
36
to
54
| You can also pin a device to a release via the CLI as follows: | ||
| - Pin to a specific release: `balena device pin 7cf02a6 91165e5` | ||
| - Track latest: `balena device track-fleet 7cf02a6` |
There was a problem hiding this comment.
repetition of info? from L18
There was a problem hiding this comment.
The commands look similar but they're not. For each section we have device vs fleet, and the second bullet is a different command track-latest vs track-fleet
myarmolinsky
force-pushed
the
update-release-policy-docs
branch
3 times, most recently
from
752e4ad
to
42b93ab
Compare
Change-type: patch
myarmolinsky
force-pushed
the
update-release-policy-docs
branch
from
42b93ab
to
c1e7fd5
Compare
vipulgupta2048
approved these changes
Apr 24, 2023
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 Policy: Update docs and screenshots
Change-type: patch