📖[Docs] How-to: Z-stream Automatic Updates#1219
📖[Docs] How-to: Z-stream Automatic Updates#1219everettraven merged 1 commit intooperator-framework:mainfrom
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1219 +/- ##
==========================================
- Coverage 76.53% 76.49% -0.05%
==========================================
Files 40 40
Lines 2340 2340
==========================================
- Hits 1791 1790 -1
- Misses 392 393 +1
Partials 157 157
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
| sourceType: Catalog | ||
| catalog: | ||
| packageName: argocd-operator | ||
| version: “~2.3" # Automatically upgrade patch releases for v2.3 |
There was a problem hiding this comment.
is 2.3.x equivalent to this?
Should we document all the semantic ways to achieve "z-stream automatic updates"?
There was a problem hiding this comment.
I don't think we need to document the synonyms for a particular version range. I think one example is sufficient here. The API reference will document all the ways.
There was a problem hiding this comment.
Yeah, that was my thought process as well. I think it's best to give folks one way of doing things (even if there are multiple - and document that elsewhere). Options lead to stress XD - having said that, is 2.3.x prettier?
There was a problem hiding this comment.
i think ~2.3 is fine. it's 1 character shorter :P
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
perdasilva
force-pushed
the
perdasilva/docs/howto-z-stream-upgd
branch
from
3bd28c3 to
d10752e
Compare
3 participants
Description
Closes #1128
Reviewer Checklist