Release v1.0.0 #300
Release v1.0.0 #300
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhmdnd The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
/retest |
| @@ -19,10 +19,12 @@ metadata: | |||
| ] | |||
| capabilities: Seamless Upgrades | |||
| categories: Monitoring,Security | |||
| olm.skipRange: '>=0.1.6 <0.1.32' | |||
| olm.skipRange: '>=0.1.6 <1.0.0' | |||
There was a problem hiding this comment.
Note for other reviewers.
This allows someone to upgrade directly to 1.0.0, which is fine since 1.0.0 is technically backwards compatible with 0.1.32. Even though 1.0.0 is technically a major version bump, it doesn't change how it's used or deployed so a direct upgrade should be safe.
If or when we release FIO 2.0.0, we'll need to update the skipRange so that 1.0.0 is the lower bound, but that will be a ways out (we don't actually know when that would happen). We may not be supporting any 0.1.* releases at that point.
|
/lgtm |
|
/retest |
|
/retest |
|
I'm expecting |
|
Manually updated the upgrade versions here openshift/release#34279 but there are still some issues with the upgrade testing scenario. We'll have to merge this through like we did with 0.1.32. |
|
@rhmdnd: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
No description provided.