We’re pleased to announce that Julia’s
release-1.0 branch now contains the set of commits we’re planning to call v1.0.2. You can view the list of commits added to this release since v1.0.1 here. As a patch release, this should be strictly non-breaking for existing code and should introduce no new features at all, just bug fixes and a few performance improvements.
We invite users, especially package authors, to test their code using a source build of Julia’s
release-1.0 branch to ensure there are no changes in behavior aside from bugs being fixed. A package evaluation run showed no regressions from v1.0.1, so we should be all set, but it’s always worthwhile to have more testing and assurance, especially for patch releases. If you run into any issues, please be sure to report them on GitHub by submitting an issue.
Assuming all is well, we plan to move forward with a v1.0.2 release after a few days.
I know a few fixes from Pkg.jl were not included in
v"1.0.1" since it had not synched in the stdlin pipeline. Could the changes in the stdlib repos be updated to the reader for Julia?
Is it possible to provide a binary build (something like a alpha/beta version)? It will help a lot to test the new versions, since there are many people who will not want to install everything needed to build julia from source. Furthermore, the build process can take a lot of time if you do not have a good computer.
This is done for
v"x.y.z-RC" so it might be nice to have it even if it is for a patch update.
Yes, as we’ve said before, at the moment we do not have the human resources to make binaries for prereleases of patch versions. If someone wants to volunteer to do that work then we can have them.
Where is the code that generates the existing (release) binaries?
Can you please describe how this can be achieved? What kind of equipment / operational system should we have to create those releases? Maybe I can help with that!
You can ask for details on the #releases channel on Slack.