On Fri, Jul 15, 2016 at 2:42 PM, David Anthoff <[email protected]> wrote:
> > These are all performance regressions, and they can be a nuisance for some > but blocking for others, and then it probably comes down to how many users > there are in each category (or what e.g. the paying customers want). I > would encourage other users to weigh in on this, might be helpful for the > core team to get more perspectives from the wider user base on this > question. > Having a release now or later doesn't really affect how soon you'll have a release that's usable for you – the work to fix the issues that are blocking for your needs be done one way or another – it only changes whether that release will be called 0.5.0 or 0.5.1. What it does affect is when others, who don't have the same requirements, will have a stable release that they can start using. The focus of the 0.5.0 release is to get to a solid implementation of a stable API with good performance for most use cases. It is *not* to make a perfect release for everyone – if we waited for that, we'd never release anything. A very large amount of work has gone into addressing performance regressions already; they are mostly addressed now, but optimization work will continue throughout the 0.5 cycle. Releases will be made in approximately monthly intervals just as with 0.4. For example, at some point I asked in #15276 whether it should get a 0.5 > label. Jeff responded that every issue tagged “regression” will get > attention before 0.5-final. It would simply be great if the core team > somehow marked issue that then got that attention. As #15276 stands right > now, I got a message saying “we will triage this”, but I never got a > message what the triage decision was. > Although it's not tagged, #15276 was very much on the radar for 0.5 performance regressions. As Jeff wrote when Viral asked "Is this now addressed? <https://github.com/JuliaLang/julia/issues/15276#issuecomment-231513485>": "No, this case is more difficult and not fixed yet. Believe me, not for lack of wanting to. <https://github.com/JuliaLang/julia/issues/15276#issuecomment-231515761>" Everyone wants this fixed, but it's a very hard problem and simply hasn't been resolved yet. I've labeled the issue as 0.5.x – it will be a priority to fix early in the 0.5.x series. The suggestion here is very simple: Try to find some way to communicate > back to the larger user base that a triage decision has been made for a > given issue. There should be some way to tell whether an issue is awaiting > triage or triage has been made (in the negative). A really simple way to do > this seems this: 1) issue has no milestone attached => triage decision has > not been made, 2) issue is attached to a milestone => triage decision has > been made. > Yes, this is a good procedure and we should try to stick to it better than we have been.
