-
Notifications
You must be signed in to change notification settings - Fork 33
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
Comments
This comment has been minimized.
This comment has been minimized.
Decide #127 |
This comment has been minimized.
This comment has been minimized.
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. |
This comment has been minimized.
This comment has been minimized.
This comment was marked as outdated.
This comment was marked as outdated.
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 Meanwhile, unsigned |
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.
The text was updated successfully, but these errors were encountered: