I thought we’d communicated this adequately and clearly, but there were some questions on Slack about what Julia 0.7 is and how it relates to 1.0, so it seems that this could use some official clarification:
- Julia 0.7 will be released with deprecations for functionality that existed in Julia 0.6 but will be removed or replaced in Julia 1.0.
- Julia 1.0 will remove all of those deprecations and add some functionality that we prevented from being implemented by those deprecations.
Aside from removed deprecations and functionality that was blocked by them, Julia 0.7 and 1.0 will be identical. This means that if a program runs on 0.7 without any warnings it should work exactly the same on 1.0. Julia 0.7 and 1.0 will be released very close together. The difference in release dates will only be as long as it takes to remove deprecations and implement blocked functionality. When you are upgrading Julia code from 0.6 you should follow this process:
- Upgrade to 0.7 and run your tests and example use cases.
- Make any changes that the deprecation warnings indicate.
- [Optional but recommended for production systems:] Run your applications in production on 0.7, paying close attention to any deprecation warnings that you may have missed and fixing them.
- Upgrade to 1.0 and run your tests and example use cases again.
- Fix any code that breaks because of deleted or changed functionality. This ideally shouldn’t happen, but sometimes deprecation warnings get missed.
Hopefully that clears things up.