Skip to content
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

Road to 1.0 #142

Open
timholy opened this issue Nov 22, 2019 · 7 comments
Open

Road to 1.0 #142

timholy opened this issue Nov 22, 2019 · 7 comments

Comments

@timholy
Copy link
Member

timholy commented Nov 22, 2019

I'd like to move the whole JuliaImages stack to version numbers >= 1.0 (see JuliaImages/Images.jl#825). Let's use this issue to collect plans for breaking changes in the near future.

Breaking changes include things like renamings, returning a different value than we used to (e.g., #129 might qualify, though rounding errors are a big ambiguous), or removing externally-visible functionality. Bug fixes, new features, performance improvements, etc., do not count as breaking, though of course they are very welcome.

@kimikage

This comment has been minimized.

@timholy
Copy link
Member Author

timholy commented Nov 22, 2019

Decide #127

@kimikage

This comment has been minimized.

@timholy
Copy link
Member Author

timholy commented Nov 23, 2019

I like the idea of it returning an Array. Though I also want to fix ReinterpreteArray. I'm thinking of writing a special iterator for it, I think that would theoretically solve the problem at least for the cases we care about in JuliaImages.

@kimikage kimikage pinned this issue Nov 24, 2019
@kimikage

This comment has been minimized.

@kimikage kimikage unpinned this issue Jul 8, 2020
@kimikage

This comment was marked as outdated.

@kimikage
Copy link
Collaborator

My personal roadmap has not changed for three years. However, because so much elapsed time has passed, I have withdrawn the roadmap. In other words, I have removed some v0.9 milestone flags.

Therefore, we may be able to release v0.9 without the saturating_* and so on. (I proposed them as a solution to a problem, but the parties to the problem have little interest in the development.)

Meanwhile, unsigned Fixed is something I would like to see its definition by v0.9. (Its functionality can be implemented in downstream packages.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants