Skip to content

switch docker links from b.gcr.io to gcr.io#1911

Merged
martinwicke merged 1 commit into
tensorflow:r0.8from
jendap:fix-docker-links
Apr 13, 2016
Merged

switch docker links from b.gcr.io to gcr.io#1911
martinwicke merged 1 commit into
tensorflow:r0.8from
jendap:fix-docker-links

Conversation

@jendap
Copy link
Copy Markdown
Contributor

@jendap jendap commented Apr 13, 2016

No description provided.

@jendap
Copy link
Copy Markdown
Contributor Author

jendap commented Apr 13, 2016

Do we want to switch the "latest" tags to point to release candidate versions? I think it is better pointing to old stable release. But that means we should during the release candidate period edit the documentation to contain explicit tags - i.e. gcr.io/tensorflow/tensorflow:0.8.0rc0 instead of gcr.io/tensorflow/tensorflow. Then for final release we should edit the links again. Too complicated?

Anyway, this time we can switch "latest" to the RC because people reading old documentation will se b.gcr.io where the latest will still point to 0.7.1 ;-)

@jendap
Copy link
Copy Markdown
Contributor Author

jendap commented Apr 13, 2016

@vincentvanhoucke you should probably also upload the next version of udacity container to gcr.io and update the readme accordingly.

@martinwicke martinwicke merged commit 31ea3db into tensorflow:r0.8 Apr 13, 2016
@jendap jendap deleted the fix-docker-links branch April 14, 2016 05:00
@Svikashini
Copy link
Copy Markdown

how to know which version of tensorflow been installed

@martinwicke
Copy link
Copy Markdown
Member

import tensorflow as tf
tf.__version__

@Svikashini
Copy link
Copy Markdown

Svikashini commented May 5, 2016

while importing sklearn inside tensorflow i got an error "No module named sklearn". How to install it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants