<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Anthony Baxter wrote:
<blockquote cite="mid200607110645.07875.anthony@interlink.com.au"
type="cite">
<blockquote type="cite">
<pre wrap="">But, the imagined costs of a new feature
during beta are illusory.
</pre>
</blockquote>
<pre wrap=""><!---->
This, I cannot agree with. The costs and risks of just continuing to
add new features all through the release process are high.</pre>
</blockquote>
I meant this particular feature.<br>
<br>
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.<br>
<br>
<br>
<blockquote cite="mid200607110645.07875.anthony@interlink.com.au"
type="cite">
<pre wrap=""> And I'm sorry, but the
release process is not something that's zero work.</pre>
</blockquote>
No doubt about that.<br>
<br>
You work is appreciated and your decisions are respected.<br>
<br>
I'm just suggesting a shift in emphasis to where the risks are.<br>
<br>
<br>
<blockquote cite="mid200607110645.07875.anthony@interlink.com.au"
type="cite">
<blockquote type="cite">
<pre wrap="">For the users, it
is a net win if this goes in.
</pre>
</blockquote>
<pre wrap=""><!---->
In the case of this feature, that's true.
</pre>
</blockquote>
<br>
It seems we're thinking along the same lines.<br>
<br>
<br>
Raymond<br>
<br>
</body>
</html>