Julia v0.6.2, the second patch release in the 0.6 series of releases, is now available on Download Julia. As with 0.6.1, binaries are available on Linux (i686, x86-64, ARM v7, AArch64), macOS, and Windows (32- and 64-bit). It contains a number of bugfixes, so we recommend that everyone currently using 0.6.1 or 0.6.0 upgrade to 0.6.2. You can see the list of commits included in 0.6.2 since 0.6.1 here. In all likelihood this will be the last 0.6 release, given how close we are to 0.7 and 1.0.
December 17
Julia v0.6.2, the second patch release in the 0.6 series of releases,
is now available on Download Julia. As with 0.6.1,
binaries are available on Linux (i686, x86-64, ARM v7, AArch64),
macOS, and Windows (32- and 64-bit). It contains a number of
bugfixes, so we recommend that everyone currently using 0.6.1 or
0.6.0 upgrade to 0.6.2. You can see the list of commits included in
0.6.2 since 0.6.1 here. In all likelihood this will be the last 0.6
release, given how close we are to 0.7 and 1.0.
Enjoy!
Visit Topic or reply to this email to respond.
To unsubscribe from these emails, click here.
Important Notice: The contents of this email are intended solely for the named addressee and are confidential; any unauthorised use, reproduction or storage of the contents is expressly prohibited. If you have received this email in error, please delete it and any attachments immediately and advise the sender by return email or telephone.
Deakin University does not warrant that this email and any attachments are error or virus free.
A dumb question - I wonder the easiest way to “upgrade”? Shall I just install the new version with all packages I need and simply leave the old version?
Unless you went with JuliaPro, which has a separate directory for storing your packages, everything will carry over from one minor version to the next. That is, all your Julia v0.6 packages will be stored in .julia/v0.6, and thus everything from 0.6.x will carry over to 0.6.y. But you would have a separate folder for v0.7, and thus you would probably have to reinstall packages when making that switch.
I never did try copy and pasting between folders (and then running Pkg.update() to hopefully fix requirement issues); not sure what the package meta data situation is like, etc. Perhaps someone knows more?
Maybe this is something the developers may consider to either elaborate for certain shortcuts or something can be improved for a quicker and easier migration from the old version to the new.
Great! I wonder if, in the future, we could get a root directory name in the tarball that reflects the version instead of the git hash, at least for releases. Eg julia-v0.6.2 instead of julia-d386e40c17.
All configuration saved in the program folder. It doesn’t pollute any other folder in system (Besides TEMP).
No registry keys.
No need for privileges.
When I say Julia I mean the installer of Julia Computing.
I might be wrong on the subject of this thread (I thought it means also version 0.6.2 of the installer).
Any chance for an checksum along with the GPG on the downloads page? Would be helpful for the less GPG savvy, whom I am guessing may be a good part of Julia’s user base.
My feeling on this is that dropping “ouncement” from “Announcement” to get “ANN” compromises clarity. As programmers, we like acronyms, but IMO, or AFAICT, the acronym ANN is ambiguous.
I personally would be grateful for a reduction in redundancy. If we really want to bike-shed a thread title I’d suggest removing “ANN” rather than expanding it, given that it’s already in the announcements category. Related to this post where I showed some other examples where the subject lines aren’t super useful on mobile.
mods - perhaps these last couple messages could be split off as off-topic from the rest of the 0.6.2 thread.
