Fix Migration Guide link#3876
Fix Migration Guide link#3876joelanford merged 3 commits intooperator-framework:v0.19.xfrom pradeepnnv:fix-migration-guide-link
Conversation
| "https://v0-19-x.sdk.operatorframework.io/docs/golang/project_migration_guide/\n" | ||
| projutil.PrintDeprecationWarning(depMsg) | ||
| } | ||
| if err := cli.RunLegacy(); err != nil { |
There was a problem hiding this comment.
It shows great and it is just missing the fragment.
See the changelog directory. we add the fragment and teh CHANGELOG it is gen over it.
There was a problem hiding this comment.
Thanks @camilamacedo86 . I added the changelog fragment. Please review.
camilamacedo86
left a comment
There was a problem hiding this comment.
/lgtm
great work 🥇
|
Thanks @camilamacedo86 . Guessing I can merge now. |
|
Hi @pradeepnnv,
The process defines that we need 2 LGTM before merging the changes. Open source is based on feedbacks and health discussions for we achieve the best result :-) Let's see if the reason for we do not point out to master branch is clear for @estroz as well and he agrees as well with it and/or if at least we can get here +1 OK. |
|
Thanks @camilamacedo86 . I'll wait for @estroz to approve before merging. |
|
I @pradeepnnv, Shows that @estroz and @joelanford for this specific scenario prefer to point out for the latest version. I just commit the @estroz suggestion. let's see if we are able to get it merged in time to ship with the next 0.19.4 release. |
Co-authored-by: Eric Stroczynski <estroczy@redhat.com>
|
@pradeepnnv Just FYI, I rebased your branch to the latest v0.19.x, which had some other necessary fixes. Hopefully the currently running CI will pass and we can get this into v0.19.4. |
Fixes #3862
This Change fixes the Link to project migration guide
Project Migration Guide link is broken.:
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments(seechangelog/fragments/00-template.yaml)website/content/en/docs