I don’t agree. Version 0.7 displays the warning in combination with an automated “translation” into the new function (that’s at least what happens for linspace: The deprecation warning is displayed, but at the same time a range command is run with the same start and stop values and a default number of 50 steps). What I want to suggest is to have the warnings/error messages in version 1.0 without the automated solution.
Currently, version 1 only throws the error “command not found”. When I ran into this issue, I was trying to recapitulate some examples I had found, which I tried to adapt to my purposes. When I got the error my first guess was that I had a typo (I tend to type uppercase characters at the beginning of a command). Then I checked the syntax, which was fine as well. It took me some time to figure out that those examples were from an older version of julia and some commands had been deprecated. As I had already seen the PSA mentioned above, I got the idea to install julia 0.7 and test the linspace command. There I got the answer and was able to solve the problem pretty quickly. However, this needed some research, that might repell other potentially new users.
I now know, that I need julia 0.7 alongside 1.0, even though I have no previous codebase that needs upgrading or workflows that need to be adopted. This is unfortunately not mentioned in the PSA.
If julia 1 had thrown the error message “command not found” together with the information about the deprecation of linspace and the hint to use range, the whole issue would have been solved much faster and more easily.