[eluser]Derek Allard[/eluser]
Hey beseku.
In the spirit of helping here, you'd want to update input.php as there were important security fixes, but beyond that, feel free to sit on it. In this case, we released a new version specifically because we found a potential security hole, and proactively fixed it. I think you'll agree that we don't want to sit on known security weaknesses. Still, this doesn't diminish your overall point, that non-security related updates have no scheduled release dates either, and make it difficult for you to plan for.
To this end, I agree with you fully, it is difficult to plan around things that you don't know. The flip side for me (EllisLab) though, is that if we give dates, we paint ourselves into corners that are untenable. For example, let's say that I said that CodeIgniter 2 is coming out August 1. Now let's say that your company makes all its plans, telling your clients, planning release dates, etc around this. Then we can't make it (for whatever reason). People get mad. This gets compounded if people like you are making business decisions based on a projected date. And people will make business decisions even if we have big disclaimers in bold red type. The reason for the delay usually doesn’t matter to people either.
Really, the whole thing just gets messy and leads to PR nightmares that can simply be avoided by just telling people to
Quote:Always, without exception, make decisions regarding EE based on what’s currently available.
I'm not unaware or unsympathetic to this from your point of view, its just that it isn't feasible for us.