{{ message }}
Create TensorBoard 0.4.0-rc1#629
Merged
Merged
Conversation
chihuahua
approved these changes
Oct 6, 2017
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

This PR starts the TensorBoard 0.4 minor series, which maps to TensorFlow 1.4.
The
0.4branch has been cut fromHEADtoday for this series. The true name of this release will be0.4.0-rc1, to conform to semver. However, intensorboard.versionand on PyPi it will be known as0.4.0rc1to conform to PEP 440. @gunan has informed me there are benefits to semver conformance, as we introduce more languages into the repository.As soon as this change is merged, this release candidate will be published to PyPi. I've confirmed that
pip install tensorflow-tensorboardwill not choose by default to install an RC.Then, I will send a PR to TensorFlow updating their setup.py to say
tensorflow-tensorboard >= 0.4.0rc1, < 0.5.0, so they can create their release candidate. I'm confident this will work.