# And now... Julia 0.6.2!

**URL:** <https://discourse.julialang.org/t/and-now-julia-0-6-2/7822>\
**Category:** Announcements\
**Tags:** release\
**Created:** [December 17, 2017, 11:00pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822 "2017-12-17T23:00:40Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![ararslan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ararslan/32/3825_2.png) [@ararslan](https://discourse.julialang.org/u/ararslan)\
**Post date:** [December 17, 2017, 11:00pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/1 "2017-12-17T23:00:40Z")

</div>

Julia v0.6.2, the second patch release in the 0.6 series of releases, is now available on [Download Julia](https://julialang.org/downloads). 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](https://github.com/JuliaLang/julia/compare/v0.6.1...v0.6.2). In all likelihood this will be the last 0.6 release, given how close we are to 0.7 and 1.0.

Enjoy!

---

<div class="post-metadata">

**Author:** ![Shpiel\_Meister](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/32.png) [@Shpiel\_Meister](https://discourse.julialang.org/u/Shpiel_Meister)\
**Post date:** [December 17, 2017, 11:07pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/2 "2017-12-17T23:07:20Z")

</div>

thx!

---

<div class="post-metadata">

**Author:** ![ngphuoc](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ngphuoc/32/4077_2.png) [@ngphuoc](https://discourse.julialang.org/u/ngphuoc)\
**Post date:** [December 17, 2017, 11:10pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/3 "2017-12-17T23:10:31Z")

</div>

The link is broken!

> [https://julialang-s3.julialang.org/bin/linux/x64/0.6/julia-0.6.2-linu](https://julialang-s3.julialang.org/bin/linux/x64/0.6/julia-0.6.2-linu)  
> x-x86\_64.tar.gz

> ```
> ararslan Committer
> 
> ```
> 
> December 17  
> Julia v0.6.2, the second patch release in the 0.6 series of releases,  
> is now available on [Download Julia](https://julialang.org/downloads). 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.

---

<div class="post-metadata">

**Author:** ![ararslan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ararslan/32/3825_2.png) [@ararslan](https://discourse.julialang.org/u/ararslan)\
**Post date:** [December 17, 2017, 11:16pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/4 "2017-12-17T23:16:45Z")

</div>

It should be fixed now. I had to correct the permissions where it’s hosted.

---

<div class="post-metadata">

**Author:** ![juliohm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juliohm/32/215266_2.png) [@juliohm](https://discourse.julialang.org/u/juliohm)\
**Post date:** [December 17, 2017, 11:17pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/5 "2017-12-17T23:17:59Z")

</div>

Thanks! git pulling now…

As a side comment, whenever I read ANN: in the title of a poster, the first thing that comes to mind is “Artificial Neural Networks” 🤓

---

<div class="post-metadata">

**Author:** ![Jordan\_Cluts](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jordan_cluts/32/13753_2.png) [@Jordan\_Cluts](https://discourse.julialang.org/u/Jordan_Cluts)\
**Post date:** [December 17, 2017, 11:22pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/6 "2017-12-17T23:22:53Z")

</div>

> [@juliohm](#):
>
> whenever I read ANN: in the title of a poster, the first thing that comes to mind is “Artificial Neural Networks”

I go through the exact same train of thought every time.

---

<div class="post-metadata">

**Author:** ![juliohm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juliohm/32/215266_2.png) [@juliohm](https://discourse.julialang.org/u/juliohm)\
**Post date:** [December 17, 2017, 11:24pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/7 "2017-12-17T23:24:40Z")

</div>

Yes, I would suggest a more explicit “Announcement:” keyword in the title instead, but that is a minor detail. 🙂

---

<div class="post-metadata">

**Author:** ![chobbes](https://avatars.discourse-cdn.com/v4/letter/c/848f3c/32.png) [@chobbes](https://discourse.julialang.org/u/chobbes)\
**Post date:** [December 18, 2017, 12:13am UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/8 "2017-12-18T00:13:28Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Elrod](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/elrod/32/22461_2.png) [@Elrod](https://discourse.julialang.org/u/Elrod)\
**Post date:** [December 18, 2017, 2:03am UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/9 "2017-12-18T02:03:59Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![chobbes](https://avatars.discourse-cdn.com/v4/letter/c/848f3c/32.png) [@chobbes](https://discourse.julialang.org/u/chobbes)\
**Post date:** [December 18, 2017, 2:33am UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/10 "2017-12-18T02:33:50Z")

</div>

> [@Elrod](#):
>
> 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.

Thanks!!

> [@Elrod](#):
>
> 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.

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [December 18, 2017, 7:42am UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/11 "2017-12-18T07:42:40Z")

</div>

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`.

---

<div class="post-metadata">

**Author:** ![RoyiAvital](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/royiavital/32/571_2.png) [@RoyiAvital](https://discourse.julialang.org/u/RoyiAvital)\
**Post date:** [December 18, 2017, 8:32am UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/12 "2017-12-18T08:32:43Z")

</div>

Any chance for portable installers for Windows?

---

<div class="post-metadata">

**Author:** ![mzaffalon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mzaffalon/32/214168_2.png) [@mzaffalon](https://discourse.julialang.org/u/mzaffalon)\
**Post date:** [December 18, 2017, 10:30am UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/13 "2017-12-18T10:30:28Z")

</div>

The Julia installer for Windows is already portable: you select the unpacking directory, set the `PATH` env variable and you are done.

---

<div class="post-metadata">

**Author:** ![RoyiAvital](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/royiavital/32/571_2.png) [@RoyiAvital](https://discourse.julialang.org/u/RoyiAvital)\
**Post date:** [December 18, 2017, 10:54am UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/14 "2017-12-18T10:54:11Z")

</div>

We have been through this discussion:

> [@ANN: The JuliaPro distribution by Julia Computing](https://discourse.julialang.org/t/ann-the-juliapro-distribution-by-julia-computing/1736/44):
>
> Any progress with Portable Version? That would be amazing to have.

> [@ANN: The JuliaPro distribution by Julia Computing](https://discourse.julialang.org/t/ann-the-juliapro-distribution-by-julia-computing/1736/45):
>
> Hello, I’m very excited by the 0.5.1.1 JuliaPro environment. On windows it feels again like the prehistoric Julia 0.2 that used to have the great “Batteries included” sticker on the box. IJulia and Juno work the first time without any collision with the various external python/atom installs. I’d like to ask where I should write the error issues (PRs?) that are specific to JuliaPro (on windows). Into JuliaLang GitHub? Or is there a different repo for this purpose? Currently I’ve encounter prob…

Portable Applications follows:

1. All configuration saved in the program folder. It doesn’t pollute any other folder in system (Besides TEMP).
2. No registry keys.
3. 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).

---

<div class="post-metadata">

**Author:** ![mzaffalon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mzaffalon/32/214168_2.png) [@mzaffalon](https://discourse.julialang.org/u/mzaffalon)\
**Post date:** [December 18, 2017, 11:22am UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/15 "2017-12-18T11:22:12Z")

</div>

Apologies, I thought you meant the standard distribution.

---

<div class="post-metadata">

**Author:** ![polypus74](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/polypus74/32/657_2.png) [@polypus74](https://discourse.julialang.org/u/polypus74)\
**Post date:** [December 18, 2017, 3:15pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/16 "2017-12-18T15:15:06Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [December 18, 2017, 3:34pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/17 "2017-12-18T15:34:43Z")

</div>

> Checksums for this release are available in both [MD5](https://julialang-s3.julialang.org/bin/checksums/julia-0.6.2.md5) and [SHA256](https://julialang-s3.julialang.org/bin/checksums/julia-0.6.2.sha256) format.

---

<div class="post-metadata">

**Author:** ![ssfrr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ssfrr/32/3736_2.png) [@ssfrr](https://discourse.julialang.org/u/ssfrr)\
**Post date:** [December 18, 2017, 4:50pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/18 "2017-12-18T16:50:33Z")

</div>

> [@juliohm](#):
>
> Yes, I would suggest a more explicit “Announcement:” keyword in the title instead, but that is a minor detail. 🙂

No! The discourse email subject lines are already epically long and often I can’t read them on my phone. Keep it compact, please.

---

<div class="post-metadata">

**Author:** ![juliohm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juliohm/32/215266_2.png) [@juliohm](https://discourse.julialang.org/u/juliohm)\
**Post date:** [December 18, 2017, 5:03pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/19 "2017-12-18T17:03:29Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ssfrr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ssfrr/32/3736_2.png) [@ssfrr](https://discourse.julialang.org/u/ssfrr)\
**Post date:** [December 18, 2017, 6:26pm UTC](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822/20 "2017-12-18T18:26:24Z")

</div>

This is how it shows up in my mail client on my phone:

![02](https://global.discourse-cdn.com/julialang/original/3X/3/e/3e081d84dfbadf8a235fbfc01b09d95304dcad67.png)

and in landscape:

 ![40](https://global.discourse-cdn.com/julialang/original/3X/0/8/08e4bcfabc683c323f9d7df6d3eae71291f21306.png)

and in the discourse header on the web:

![image](https://global.discourse-cdn.com/julialang/original/3X/0/c/0ce676a5649a2ca15f2c0498e6d0f42e22d89616.png)

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](https://discourse.julialang.org/t/shorter-email-subject-lines/6545) 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.

[Next page](https://discourse.julialang.org/t/and-now-julia-0-6-2/7822.md?page=2)