Julia 0.7.0-alpha is now available

release

#1

The Julia developers are pleased to announce that the alpha version of Julia v0.7.0 is now available. You can find it in the “upcoming release” section of the downloads page at https://julialang.org/downloads. Alpha binaries are available right now for Linux (x86-64 and i686), macOS, and Windows (32- and 64-bit).

As an alpha, this is not production ready; it’s intended to give people the chance to get a feeling for what a 0.7 release will be like, start getting their code up to date, and test for issues. Most users should continue to use the latest release, 0.6.3, until 0.7.0 is fully released.

That said, we encourage everyone to try out 0.7.0-alpha and let us know on GitHub (https://github.com/JuliaLang/julia/issues) if you run into any problems. Bugs identified in the alpha will be fixed in the beta release. For folks who use Julia on Travis CI, the release of the alpha also means that 0.7 is now available along with 0.6 and nightly as a version choice, so now is a good time for package developers to add 0.7 to their testing matrices, if they haven’t already.

Enjoy!


#2

Hurrah for the developers!


#3

Quick link to the release notes:


#4

As for the packages in METADATA, is it time to start supporting 0.7.0? I mean, to remove all those deprecation warnings or should we wait beta because things can change?


#5

Probably best to wait for FemtoCleaner.jl to be updated so it can autodeprecate your entire codebase.


#6

It’s time to start trying. Alpha is when we try to update everything and break it. Beta is when they fix all the bugs we found so we can finish updating. So I would recommend updating in alpha so you can start reporting :wink:


#7

What is taking you so long on on DifferentialEquations.jl? I want to solve a DAE on v0.7! :wink:


#8

I’m the biggest hypocrite. I’m not even going to try until Femtocleaner is out :smile:, well and also after my defense is done. I don’t want to find out the list of things I need to fix right before my defense :wink:. But after that…


#9

Good luck with your defense !


#10

This is my write-up based on the 0.7.0-alpha change-log.

https://white.ucc.asn.au/2018/06/01/Julia-Favourite-New-Things.html

It is a fair bit shorter than the the full change log, and might so it not capture everything you’re interested in (It also intentionally skips several of the headline new features.)
it is after all just a few of my Favourite Things.


#11

No mention of Pkgs tied up with Strings…?


#12

That’s a very good excuse.

I’d actually be quite interested in helping with DifferentialEquations: I’ve updated a number of packages to 0.7 now (notably DataFrames and JavaCall) and I haven’t gotten nearly as much of a chance to mess around with DifferentialEquations as I’d like to, mostly just admiring it from afar. (Maybe that means I’d be a bad person to help out, but that’s why we have unit tests.) I’m not sure if I’ll get a chance to do it because I have to focus on the packages I need to use first. Does DifferentialEquations have any simpler dependencies that need updating? I have a feeling we may have some of those in common.

Is FemtoCleaner really expected to be “fire and forget”? My expectation was that there would still be a lot of manual changes needed, but it it’s all automated that would be really awesome.


#13

In v0.5 -> v0.6 there’s a lot less manual work than I expected. I only had like 2-3 packages which actually needed a good look.

Tons. ForwardDiff, Optim, NLsolve, Requires, Reexport, DataStructures, etc. There’s quite a big list of common packages that we use.

https://juliaobserver.com/packages?depended_id=DifferentialEquations


#14

Is it safe/possible to have 0.7 alpha installed alongside 0.6.3 on Windows?


#15

Yes, they shouldn’t conflict.


#16

Is there any documentation on how to migrate an existing package to the new package manager?


#17

There is some info in this thread: JuliaRegistries: is it now possible to add packages here?


#18

Just in case someone was wondering: it doesn’t seem to be safe to install 0.7 Alpha alongside an earlier 0.7 development version. I did that, and I believe that messed up both versions. I had to do a clean reinstall. (Of just 0.7 Alpha, at the moment.)


#19

Can anyone please verify if this bug is reproducible:

AFAIK this will not work correctly, because both will use the same directories (~/.julia/v0.7) (am I right?). On the other hand, you can use v0.6 and v0.7 side-by-side without problem.


#20

dear All, many thanks for this important step for Julia. However I have trouble getting the Linux 32bits version installed (the 64bits one is OK); its seems the “gz” file is truncated :

[davidj@golden tmp]$ /bin/time wget https://julialang-s3.julialang.org/bin/checksums/julia-0.7.0-alpha.sha256
--2018-06-06 10:26:56--  https://julialang-s3.julialang.org/bin/checksums/julia-0.7.0-alpha.sha256
Résolution de julialang-s3.julialang.org… 151.101.54.49, 2a04:4e42:600::561, 2a04:4e42:400::561, ...
Connexion à julialang-s3.julialang.org|151.101.54.49|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 675 [application/octet-stream]
Sauvegarde en : « julia-0.7.0-alpha.sha256 »

julia-0.7.0-alpha.sha256                   100%[======================================================================================>]     675  --.-KB/s    ds 0s      

2018-06-06 10:26:57 (17,4 MB/s) — « julia-0.7.0-alpha.sha256 » sauvegardé [675/675]

0.05user 0.00system 0:00.73elapsed 7%CPU (0avgtext+0avgdata 23840maxresident)k
0inputs+8outputs (0major+473minor)pagefaults 0swaps
[davidj@golden tmp]$ /bin/time wget https://julialang-s3.julialang.org/bin/linux/x86/0.7/julia-0.7.0-alpha-linux-i686.tar.gz
--2018-06-06 10:27:27--  https://julialang-s3.julialang.org/bin/linux/x86/0.7/julia-0.7.0-alpha-linux-i686.tar.gz
Résolution de julialang-s3.julialang.org… 151.101.54.49, 2a04:4e42:600::561, 2a04:4e42:200::561, ...
Connexion à julialang-s3.julialang.org|151.101.54.49|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 143060786 (136M) [application/x-gzip]
Sauvegarde en : « julia-0.7.0-alpha-linux-i686.tar.gz »

julia-0.7.0-alpha-linux-i686.tar.gz        100%[======================================================================================>] 136,43M   313KB/s    ds 7m 26s  

2018-06-06 10:35:27 (313 KB/s) — « julia-0.7.0-alpha-linux-i686.tar.gz » sauvegardé [143060786/143060786]

7.60user 6.15system 8:00.30elapsed 2%CPU (0avgtext+0avgdata 23904maxresident)k
184inputs+279912outputs (0major+480minor)pagefaults 0swaps
[davidj@golden tmp]$ env LC_ALL=C sha256sum -c julia-0.7.0-alpha.sha256 2>/dev/null | grep julia-0.7.0-alpha-linux-i686.tar.gz
julia-0.7.0-alpha-linux-i686.tar.gz: OK
[davidj@golden tmp]$ /bin/time gunzip -k julia-0.7.0-alpha-linux-i686.tar.gz

gzip: julia-0.7.0-alpha-linux-i686.tar.gz: invalid compressed data--crc error

gzip: julia-0.7.0-alpha-linux-i686.tar.gz: invalid compressed data--length error
Command exited with non-zero status 1
8.42user 4.96system 0:24.44elapsed 54%CPU (0avgtext+0avgdata 10000maxresident)k
560inputs+992864outputs (1major+191minor)pagefaults 0swaps

Could somebody check it ? Or am I wrong in some way ?
regards,
Jacques David