(original) (raw)
Anthony Baxter wrote:I meant this particular feature.But, the imagined costs of a new feature during beta are illusory.This, I cannot agree with. The costs and risks of just continuing to add new features all through the release process are high.
In general, there ought to be some distinction between patches that affect everything (i.e. AST) and patches that affect a tiny portion of the universe (a new itertool or Tim's patch) -- the latter tend to be poorly exercised during beta releases anyway, so we are kidding ourselves about the impact of putting them in a second beta. IMO, the most substantial risks we have with Py2.5 still lie with the big changes that went in early. The SF tracker indicates that these are still not fully debugged.
No doubt about that.And I'm sorry, but the release process is not something that's zero work.
You work is appreciated and your decisions are respected.
I'm just suggesting a shift in emphasis to where the risks are.
For the users, it is a net win if this goes in.In the case of this feature, that's true.
It seems we're thinking along the same lines.
Raymond