doc: clarify which snap channels to use for production-ready version #264
Conversation
This file contains hidden or 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
Signed-off-by: Ruth Fuchss <ruth.fuchss@canonical.com>
ru-fu
requested review from
markylaing,
masnax,
roosterfish and
tomponline
as code owners
tomponline
approved these changes
Feb 19, 2024
roosterfish
approved these changes
Feb 20, 2024
Contributor
roosterfish
left a comment
roosterfish
left a comment
There was a problem hiding this comment.
Looks good! Just for clarification, if you don't specify the channel, it still picks the stable one right?
Author
It picks the default channel defined by each snap. Those are the documented ones except for MicroCeph (where the default is now reef/stable) - but those might in theory change at any time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
No description provided.