-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Release 2.0.0 #103
Release 2.0.0 #103
Conversation
a30e953
to
6465af3
Compare
Might want to consider #108 |
README.md
Outdated
|
||
* `GlobeCoordinateValue` does not accept empty strings as globes any more. | ||
* `GlobeCoordinateValue` does not accept precisions outside the [-360..+360] interval any more. | ||
* Changed hash calculation of `GlobeCoordinateValue` to be more robust. |
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.
Shouldn't this explicitly say the hash change was a backwards incompatible one? I know "robust" is supposed to mean it here but if does not immediately strike as a breaking change IMO.
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.
Done.
README.md
Outdated
@@ -93,8 +93,11 @@ It is based upon and contains a lot of code written by [Jeroen De Dauw] | |||
|
|||
## Release notes | |||
|
|||
### 2.0.0 (dev) | |||
### 2.0.0 (2017-05-08) |
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.
Deprecation still missing
Please have a look at the 2.0.0 milestone. Because we changed a hash calculation in an incompatible way, we need to do a major version bump anyway. We might as well include all previously proposed breaking changes.