A lot of people are posting issues where their old code doesn’t work anymore on 1.0 because some function has been renamed or removed. The 0.7 release exists exactly for this reason: your old code will work on 0.7 and give you a specific warning about how to fix your code. If you have any old code, …

Stef, Of course, there are problems with 1.0, fortunately there still is some work to do! Before Julia, there was no problem with Julia…! But was it better? There are always more problems with the future than with the past, and Julia is made for the future! What you have done is not perfect, but…

I would tend to say that almost no one should use 1.0 day-to-day for the next month or so, until most packages have fully upgraded. There is zero advantage to using 1.0 over 0.7 right now (except for testing), just more non-functioning packages, because 1.0 is just 0.7 minus deprecations.

Yes. After this process, it has occurred to me that it might have been better to release 1.0 with deprecations and then delete them in 1.1 but that’s not what we did, but that occurred to me only after the fact, so ¯\_(ツ)_/¯

[image] stevengj: There is zero advantage to using 1.0 over 0.7 right now (except for testing), just more non-functioning packages, because 1.0 is just 0.7 minus deprecations. Will the (minor) changes in the short run be backported to v0.7?

In case you use 0.7 to upgrade a package: do test on 1.0 as well, even if it is without warnings on 0.7. Two possible gotchas are overloading a method that no longer exists in Base and the fact that precompile is the default in 1.0.

[image] StefanKarpinski: Yes. After this process, it has occurred to me that it might have been better to release 1.0 with deprecations and then delete them in 1.1 but that’s not what we did, but that occurred to me only after the fact, so ¯_(ツ)_/¯ Everyone makes mistakes, but not everybody i…

What would have happened if Pkg3 in 1.0 were to have assumed an upper bound on dependencies in legacy REQUIRE files, so that only releases tagged for 1.0 could be added? Would that have made things better or worse from a new user perspective?

I think this could be very confusing for people new to Julia (and maybe even not so new). Is it reasonable to turn errors into deprecation warnings in 1.0 (or 1.0.x )? And then release 1.1 ASAP, when most packages are upgraded ? I know that’s what 0.7 is for, but it would be easier for people to…

I’ve worked out some heuristics for when a package is or is not compatible with 0.7 which I will try to get into the script that generates the General registry soon.

btw: How should i understand “Unfortunately that’s a bug in Julia that is fixed on 1.0 but not on 0.7.” that was recently on slack (by staticfloat?). I thought 1.0 is 0.7 without deprecations only?

PSA: use Julia 0.7 if you are upgrading

Announcements

Topic		Replies	Views
What is Julia 0.7? How does it relate to 1.0? Internals & Design	6	8912	June 17, 2018
Moving from v0.6 to v1.0 has been so annoying General Usage	36	3504	October 4, 2018
Julia v1.0-rc1 is now available Announcements release	60	6782	August 16, 2018
Warning in 1.0 +? General Usage	28	1770	March 3, 2020
1.0 adoption path? General Usage	76	14510	July 21, 2018

PSA: use Julia 0.7 if you are upgrading

Related topics