Release prioritisation and cadence

[ursi]

@i-am-the-slime

Yes, I think the lack of support for what I’m suggesting tells me you’re right about this. I seem to be one of these petty vocal minorities, so I’ll stop arguing for this.

@hdgarrood

I don’t think you’re necessarily in the minority here. I would just like to see more evidence that the community would like us to shift in the direction of having more frequent and smaller breaking change releases before going ahead and doing it

Just commenting to say that I also support implementing new features when they’re ready as opposed to waiting and batching them together.

[ursi]

I’ll also add a pro to this that hasn’t been mentioned yet: the more time something has been used, the more likely you are too find bugs/improvements. It sounds like we could have had 500 more days worth of scrutiny on ES modules if it were merged when it was ready, and I don’t think that’s a negligible loss.

[hdgarrood]

That’s true, but it was quite far off being ready when it was first opened. I haven’t looked in a lot of detail recently, but I don’t think it’s quite ready even now.