-
Notifications
You must be signed in to change notification settings - Fork 836
Rename Tf to TF #332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename Tf to TF #332
Conversation
|
And, I think the doc should be updated, too. |
|
Good job! @ScorpioCPH I agree with @gaocegege and we'd better update the docs in the same PR to keep the unity. |
|
@gaocegege @DjangoPeng Thanks, done. |
|
Can you provide examples of K8s resources to show that is the convention in Kubernetes? |
|
@jlewi Sure, this is coding-conventions and api-conventions. For example here: We chose |
854e496 to
1938067
Compare
|
My take on K8s API here is that they use the generally accepted capitalization e.g.
I'm convinced that TFJob is better. Lets give people until Monday to chime in; I'll post to slack. I don't want to have to change it again. |
|
/cc @wbuchwalter |
|
+1 for |
|
+1 |
|
@ScorpioCPH We have to rebase the PR. |
1938067 to
d6a9510
Compare
|
/test tf-k8s-presubmit |
|
@jlewi PTAL, |
|
Looks like the tests failed. |
|
/test all |
|
Looks like the test failure was because we ran out of disk space. let me clean it up. |
|
/test tf-k8s-presubmit |
|
Merged. @jlewi We'd better start squash merging in the next PR. |
|
@DjangoPeng yes please always do squash merge. |
…beflow/trainer#332 This was causing an error `error: unable to recognize "config.yaml": no matches for tensorflow.org/, Kind=TfJob` where the Kind of job was not identified by following the README. Updated the reference so that people following the guide don't face the same trouble in the future. Bunch of other spell corrects :)
As we discuss here #328
Rename
TftoTFto make more conventional. Fixes #328.@jlewi PTAL.
This change is