I just wanted to share my experience in moving from v0.6.4 to 1.0. I have to say, it has been extremely annoying, and I am wondering why I choose to work in Julia. The developers should have in mind there are several people out there who just want to use this language for scientific analysis, and it…

[image] PSA: use Julia 0.7 if you are upgrading Announcements 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…

There’s been quite a few topics on this over the past week, and to some degree I suppose that’s unavoidable when putting out a major release with (by definition) breaking changes. Just thought I’d throw in two pieces of info that you might well be aware of but if you aren’t might be helpful: If y…

My understanding of version 0.x software is that it’s considered unreliable and likely to change without notice: Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable. (From the semantic versioning site) Perhaps th…

[image] nilshg: you might want to consider upgrading to 0.7 first I think you should state that more strongly: One should absolutely and unequivocally upgrade to 0.7 first, if one is updating a codebase. At least do it if you’re considering writing a frustrated post complaining about the upgr…

[image] masiddique: I have to revise so much of my code now. I am not sure what you would prefer. Languages change, usually for the better, do you want that not to happen? Only abandoned and dead languages keep their API forever. While automated tools like FemtoCleaner can’t fix everything, …

Thank you for this information. I wasn’t aware of how important it would be to upgrade to 0.7 before moving to 1.0, or to use FemtoCleaner either. Sure, I’ll like to read them, but I’m more of a Julia user than developer. Thanks for responding though.

Even though some of these changes are frustrating as a user, if you try to put yourself in the language designer shoes, you’ll find they usually are the right choice (or at least an improvement over the previous situation). And if you search a bit on the forum or github, you often find explanations . …

It’s good that you have asked/complained! I have read and think that it probably would have been better to name 0.7 as 1.0 and ‘our 1.0’ as 1.1. Now it’s too late and really important to comunicate again and again to use 0.7 first when upgrading to 1.0 (or 1.0.1). Btw. you can mark the answer from …

[image] swissr: I have read and think that it probably would have been better to name 0.7 as 1.0 and ‘our 1.0’ as 1.1. That approach would not have been without its issues though. Experience has shown that people really hate to fix deprecation warnings. Somehow they’d much rather just live wi…

Wouldn’t it also mean giving up semantic versioning?

Moving from v0.6 to v1.0 has been so annoying

General Usage

Sukera October 1, 2018, 4:08pm 3

Topic		Replies	Views
Warning in 1.0 +? General Usage	28	1760	March 3, 2020
PSA: use Julia 0.7 if you are upgrading Announcements psa	24	6728	August 15, 2018
Julia v1.0-rc1 is now available Announcements release	60	6733	August 16, 2018
Tips for updating code for 0.7 General Usage	16	3394	March 30, 2018
What is Julia 0.7? How does it relate to 1.0? Internals & Design	6	8911	June 17, 2018

Moving from v0.6 to v1.0 has been so annoying

Related topics