[CE-715]Fixed the fabric operator image path issue #45
Conversation
litong01
requested review from
hightall,
jiahaoc1993 and
yeasy
as code owners
Haitai, my understanding is that we should continue use jira for issue tracking. I would like to just use github issues for that though. |
confirmed with brent (earlier with Ry), we will be continuing using jira for issue tracking. So please do not create issues on this repo. |
litong01
changed the title
|
@litong01 I think we need to discuss it at this weekly meeting, I can not find any benefits of using jira after migrate to GitHub to manage code. Issue is native support of GitHub, and can connect PR with it, why to use jira? |
|
I have also placed the jira issue reference in the title of the pull request. |
you haven't update title of the commit message. For quick solution, please update the title of your commit message, and this PR can be merged, and we need discuss the tracking system this Friday. I can't understand why still use jira. |
|
@hightall the title has been changed. |
this shown only one commit, and the commit message not include the jira number. |
Since the fabric operator image is now officially being placed on docker hub, we need to change the operator deployment script to reflect that change and modify the README.md accordingly. This patch fixes these issues. Signed-off-by: Tong Li <litong01@us.ibm.com>
[CE-715]Since the fabric operator image is now officially
being placed on docker hub, we need to change the
operator deployment script to reflect that change
and modify the README.md accordingly. This patch
fixes these issues.