-
-
Couldn't load subscription status.
- Fork 1k
Bump to version 0.1.2 #553
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fine by me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice changes! a few things:
1 if were gonna patch often, do we need more placeholders for minor changes 0.0.1_2(like pt does)
2 ill try to look into automatic deployment of the docs/tutorials with every release of master. until then, let me know when you cut the release and ill update them accordingly
I'd prefer not to succumb to version inflation by hiding changes in a subpatch 😉 Also, PyTorch's subpatch versioning is a pain, since they don't follow Semver and are incompatible with the |
|
Possibly waiting on https://github.com/null-a/pyro/commit/b84cc99f0f2edb02f069af67115cb0eecf52fa96 ... |
856d9a8 to
f83be2c
Compare
|
waiting for tests |
|
Waiting on #560 ... |
This minor patch release contains:
(this is not strictly backward compatible, but we assume nobody is using
pyro.LambdaPoutinedirectly)