My current thinking, which may well change, is that we should make relatively frequent major releases after 1.0 – maybe once a year. Major releases should include significant functionality enhancements and some breaking changes, but not so bad that switching is a total nightmare. Making large breaking changes without immediate reward has not gone very well for Python and Perl (if you even consider Perl 6 the same language as Perl 5). Ruby seems to be doing better with the 1.x to 2.0 transition. I suspect that this is largely because the performance improvements provided RVM are so substantial.
On Sat, Aug 2, 2014 at 2:36 PM, Ivar Nesje <[email protected]> wrote: > How come I did not notice. I hope we never make stupid enough mistakes in > 1.0 that we will ever need a 2.X release (and even worse a 3.0 release). > > kl. 20:27:35 UTC+2 lørdag 2. august 2014 skrev Jacob Quinn følgende: >> >> Do note that the imminent release is **0.3**, not *3.0*. There's been a >> little confusion around about Julia's versioning, so just thought I'd >> clarify. >> >> >> On Fri, Aug 1, 2014 at 8:35 AM, Daniel Carrera <[email protected]> >> wrote: >> >>> Thanks! >>> >>> >>> On 1 August 2014 14:04, Ivar Nesje <[email protected]> wrote: >>> >>>> https://github.com/julialang/julia/blob/master/NEWS.md >>>> >>>> Currently we only have caching of object code for Base, but there is >>>> some tricks you can use to include extra packages in addition to Base when >>>> you compile. >>>> >>>> kl. 14:00:23 UTC+2 fredag 1. august 2014 skrev Daniel Carrera følgende: >>>>> >>>>> Hello, >>>>> >>>>> As the title suggests, I'd like to know what are the key features or >>>>> improvements in the upcoming Julia 3.0 (whenever it is released). >>>>> >>>>> One feature that I hope to see is either faster compiles or caching. >>>>> One of the big selling points of Julia is its speed, but the fact that it >>>>> has to recompile itself constantly every time you run a program really >>>>> gets >>>>> in the way of performance. I imagine that the solution is to cache object >>>>> code so that you only compile the stuff that has changed since the last >>>>> run. I am also sure that this is easier said than done. Does Julia 3.0 >>>>> include any work in this area? >>>>> >>>>> Cheers, >>>>> Daniel. >>>>> >>>> >>> >>> >>> -- >>> When an engineer says that something can't be done, it's a code phrase >>> that means it's not fun to do. >>> >> >>
