Skip to content

Commit

Permalink
Version 0.8.0 (#175)
Browse files Browse the repository at this point in the history
  • Loading branch information
kimikage authored Feb 3, 2020
1 parent 03057d4 commit a6e2c1d
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .travis.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ os:
- osx
julia:
- 1.0
- 1.2
- 1
- nightly
notifications:
email: false
Expand Down
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name = "FixedPointNumbers"
uuid = "53c48c17-4a7d-5ca2-90c5-79b7896eea93"
version = "0.7.0"
version = "0.8.0"

[compat]
julia = "1"
Expand Down

9 comments on commit a6e2c1d

@kimikage
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/8809

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:

git tag -a v0.8.0 -m "<description of version>" a6e2c1d0c0fd69d81226fef062d0bb313abeb0de
git push origin v0.8.0

@SimonDanisch
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this release breaking?

@kimikage
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by that?
FixedPointNumbers v0.8 is currently not used in many packages in the JuliaGraphics/JuliaImages, due to major changes in ColorTypes.jl and Colors.jl and their delays of tag releasing. (We are almost ready for release.)
Since v0.7, FixedPointNumbers has many changes, including breaking changes. Due to the reason above, the compatibilities have not been sufficiently verified.

@timholy
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you look at the change log, most of the differences are in return types, allowed bounds, and returned numeric values. If you're not sensitive to these issues, it's probably not terribly breaking.

@SimonDanisch
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I looked at the logs and wasn't really sure if it was willingly breaking, or just minor changes that shouldn't break anything but may... ;)
Thanks for the clarification :)

@timholy
Copy link
Member

@timholy timholy commented on a6e2c1d Feb 26, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You might expect ulp-level breakages to a few tests. And possibly need to convert some @test_brokens into @test, but that's the kind of breakage we can all live with!

@kimikage has done wonders for the internal machinations of this package, it's a faster and far more accurate & elegant package than it was a few months ago.

@SimonDanisch
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome :) I'm not complaining at all, just couldn't figure out immediately from the logs, how careful I need to be with upping the compat bounds!

@kimikage
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BTW, I (or we) plan to improve the arithmetic in the next v0.9, but we may have to release the patches for v0.8, so I'm suspending the improvement now.

Please sign in to comment.