I work at a small consulting company who’s primary business involves solving large scale PDE constrained optimization problems. Back in 2015 we decided to move our code base from fortran into Julia - it was a painful process at times but has more than paid off with greatly reduced development times. A huge thank you to everyone who has contributed to the development of the language!
We are currently still running Julia 1.0.2 as #30679 has broken a large portion of our code on the 1.0.3 and 1.1 releases. This has been fixed now on master, however it looks as though #31435 is going to prevent us from using 1.2 when it comes out unless it get addressed before the release.
We have been able to modify some of our code to run under 1.1 and we see a significant improvement in the speed of those codes - this is great! I’m very eager to be able to pass those speedups on to our clients but I’m concerned that we are going to have to have to stay on 1.0.2 again after 1.2 comes out as a result of #31435. We will get a pull request submitted shortly to provide a potential fix, however it is somewhat hard to do that without understanding the intent and desired behaviour of the of the commit that caused the problem in the first place.
I’m interested in any advice anyone can provide on how we may be able to overcome these difficulties. Is it possible to get an increase in the frequency of patch releases? We would be happy to help out with this if we can, but I wouldn’t know where to start on that front.