Python 2.5.3：调用补丁 [英] Python 2.5.3: call for patches
问题描述
几周后，我们将发布Python 2.5.3。这将是Python 2.5的最后一个
错误修复版本，之后，2.5的未来版本将仅包含安全修复程序，并且没有二进制文件（对于Windows或OSX）将
再次提供（来自python.org）。
原则上，该版本将包括已经发生的所有更改
subversion [1]中的release25-maint分支。如果您认为应该考虑具体的
更改，请在错误跟踪器中创建一个问题
[2]，并将其标记为2.5.3版本。已经在Python 2.6中发布了更改的后退，但可能适用于2.5的特殊兴趣。
问候，
Martin
[1] http://svn.python.org/projects/pytho...lease25-maint/
[2] http://bugs.python.org/
Within a few weeks, we will release Python 2.5.3. This will be the last
bug fix release of Python 2.5, afterwards, future releases of 2.5 will
only include security fixes, and no binaries (for Windows or OSX) will
be provided anymore (from python.org).
In principle, the release will include all changes that are already on
the release25-maint branch in subversion [1]. If you think that specific
changes should be considered, please create an issue in the bug tracker
[2], and label it with the 2.5.3 version. Backports of changes that
are already released in Python 2.6 but may apply to 2.5 are of
particular interest.
Regards,
Martin
[1] http://svn.python.org/projects/pytho...lease25-maint/
[2] http://bugs.python.org/
推荐答案
" Martin v.L ?? wis" < ma **** @ v.loewis.dewrites：
"Martin v. L??wis" <ma****@v.loewis.dewrites:
几周后，我们将发布Python 2.5.3。
Within a few weeks, we will release Python 2.5.3.
我很高兴见到这一点。感谢所有参与
协调Python版本的工作。
为了减少混淆，我可以请求任何
宣布预发布版本的2.5.3（或任何其他Python
版本）*没有*说一个??释放：一个非真正的发布
版本的Pythona ??。
看到主题公告的进展非常令人困惑
字段如下：
发布：Python 2.8.not-ready-yet
发布：Python 2.8.alpha-1
发布：Python 2.8.beta -1
发布：Python 2.8.beta-2
发布：Python 2.8发布候选1
发布：Python 2.8发布候选2
发布：Python 2.8 final
单词a ?? RELEASEDa ??这是一个强有力的指标，表明新版本的g />
Python（在这种情况下）*已发布*，而不仅仅是在
预发布表格中提供。在上面列表中唯一符合条件的是
最后一个Python 2.8实际*已发布。否则，
这个词会因为含义过多而过重，并且没有强烈表示
。
这将是如果单词a ?? releasea ??在这样的
公告中保留了该版本*的发布*（在这个
的情况下，2.8），而不是某些预发布的可用性。或许
只需使用单词a ?? ANNOUNCEDa ??或缩写为?? ANNa ??：
[ANN] Python 2.8.not-ready-yet
[ANN] Python 2.8.alpha-1
[ANN] Python 2.8.beta-1
[ANN] Python 2.8.beta-2
[ANN] Python 2.8发布候选1
[ANN] Python 2.8发布候选人2
[ANN] Python 2.8 final
那对我至少来说，传达了什么实际上发生的事情远远超过了b $ b更好，并且导致对释放状态的混淆减少。
我记得在不久之前提出这一点以产生积极影响（谢谢
你！），但似乎在最近的Python 2.6的b $ b公告发布中被忽略了。我当时并不想抱怨，
如此好的工作是由Python 2.6发布
团队完成的。
是否有一些政策文件或发布管理指南可以为发布团队更新以便跟进，而无需每次都讨论这个讨论？
-
\ a ??我曾经在消防栓工厂工作。你不能在附近的任何地方停车|
` \。 a ?? Steven Wright |
_o__）|
Ben Finney
I''m glad to see this. Thank you to all involved in the ongoing work of
coordinating Python releases.
Can I request, in the interest of reducing confusion, that any
announcements of pre-release versions of 2.5.3 (or any other Python
release) be announced *without* saying a??RELEASED: A not-really-release
version of Pythona??.
It''s very confusing to see a progression of announcements with subject
fields like:
RELEASED: Python 2.8.not-ready-yet
RELEASED: Python 2.8.alpha-1
RELEASED: Python 2.8.beta-1
RELEASED: Python 2.8.beta-2
RELEASED: Python 2.8 release candidate 1
RELEASED: Python 2.8 release candidate 2
RELEASED: Python 2.8 final
The word a??RELEASEDa?? is a strong indicator that a new version of
Python (in this case) is *released*, not merely available in a
pre-release form. The only one that qualifies in the above list is the
last one where Python 2.8 is *actually* released. Otherwise, the word
becomes overburdened with too many meanings and doesn''t indicate
anything strongly.
It would be much less confusing if the word a??releasea?? in such
announcements was reserved for the release *of that version* (in this
case, 2.8), and not for the availability of some pre-release. Perhaps
simply using the word a??ANNOUNCEDa?? or abbreviated a??ANNa??:
[ANN] Python 2.8.not-ready-yet
[ANN] Python 2.8.alpha-1
[ANN] Python 2.8.beta-1
[ANN] Python 2.8.beta-2
[ANN] Python 2.8 release candidate 1
[ANN] Python 2.8 release candidate 2
[ANN] Python 2.8 final
That, to me at least, communicates what''s actually happening far
better and leads to less confusion about what the state of release is.
I recall making this point some while ago to positive effect (thank
you!), but it seems to have been ignored in the recent progression of
announcements for Python 2.6. I didn''t want to complain at that point,
with such a good job being done otherwise by the Python 2.6 release
team.
Is there some policy document or release management guide that could
be updated for release teams to follow on this without needing to have
this discussion every time?
--
\ a??I used to work in a fire hydrant factory. You couldn''t park |
`\ anywhere near the place.a?? a??Steven Wright |
_o__) |
Ben Finney
Ben Finney写道：
Ben Finney wrote:
" Martin v.L ?? wis" < ma **** @ v.loewis.dewrites：
"Martin v. L??wis" <ma****@v.loewis.dewrites:
>在几周内，我们将发布Python 2.5.3。
>Within a few weeks, we will release Python 2.5.3.
我很高兴见到这一点。感谢所有参与
协调Python版本的工作。
为了减少混淆，我可以请求任何
宣布预发布版本的2.5.3（或任何其他Python
版本）*没有*说一个??释放：一个非真正的发布
版本的Pythona ??。
看到主题公告的进展非常令人困惑
字段如下：
发布：Python 2.8.not-ready-yet
发布：Python 2.8.alpha-1
发布：Python 2.8.beta -1
发布：Python 2.8.beta-2
发布：Python 2.8发布候选1
发布：Python 2.8发布候选2
发布：Python 2.8 final
I''m glad to see this. Thank you to all involved in the ongoing work of
coordinating Python releases.
Can I request, in the interest of reducing confusion, that any
announcements of pre-release versions of 2.5.3 (or any other Python
release) be announced *without* saying a??RELEASED: A not-really-release
version of Pythona??.
It''s very confusing to see a progression of announcements with subject
fields like:
RELEASED: Python 2.8.not-ready-yet
RELEASED: Python 2.8.alpha-1
RELEASED: Python 2.8.beta-1
RELEASED: Python 2.8.beta-2
RELEASED: Python 2.8 release candidate 1
RELEASED: Python 2.8 release candidate 2
RELEASED: Python 2.8 final
我不同意。这些确切地说出了发生了什么并告诉我我想要什么
知道，这是新的东西已经发布，也就是说，
可供下载。
I disagree. These say exactly what has happened and tell me what I want
to know, which is that something new has been released, which is to say,
made available for download.
[ANN] Python 2.8.not-ready-yet
[ANN] Python 2.8.alpha-1
[ANN] Python 2.8.beta-1
[ANN] Python 2.8.beta-2
[ANN] Python 2.8发布候选1
[ANN] Python 2.8发布候选人2
[ANN] Python 2.8 final
至少对我而言，传达了实际发生的事情远远好于
，可以减少对发布状态的混淆。
[ANN] Python 2.8.not-ready-yet
[ANN] Python 2.8.alpha-1
[ANN] Python 2.8.beta-1
[ANN] Python 2.8.beta-2
[ANN] Python 2.8 release candidate 1
[ANN] Python 2.8 release candidate 2
[ANN] Python 2.8 final
That, to me at least, communicates what''s actually happening far
better and leads to less confusion about what the state of release is.
我不同意。 [ANN]可能意味着什么：有计划的？取消？需要帮助吗？
（哦，''已发布''，为什么你不这么说？）它没有说明是什么
正在发生或分发的状态，但只是陈述一个主题。
Martin的帖子宣布Python 2.5.3为主题，但后来继续
请求特定类型的帮助。我认为你不会很高兴
或者是[ANN] Python xywhatever released。
如果你想更换RELEASED，建议一些简短的不太难看
通信发布在python.org并且可以下载，
安装，测试和使用至少也是如此。 （我目前正在使用
3.rc1;剩下的问题目前不会影响我，我接受
风险，我认为风险很小，进一步的变化会影响代码I
现在写。）
tjr
I disagree. [ANN] could mean anything: planned? canceled? needs help?
("Oh, ''released'', why didn''t you say so?") It says nothing about what
is happening or the state of a ''distribution'' but merely states a topic.
Martin''s post announced Python 2.5.3 as the topic, but then went on to
request a specific type of help. I presume you would not be happy
either with "[ANN] Python x.y.whatever released".
If you want RELEASED replaced, suggest something short and not too ugly
that communicates "posted at python.org and available to be downloaded,
installed, tested, and used" at least as well. (I am currently using
3.rc1; the remaining problems do not currently affect me and I accept
the risk, which I view as small, that further changes will affect code I
write now.)
tjr
Terry Reedy< tj*****@udel.eduwrites：
Terry Reedy <tj*****@udel.eduwrites:
Ben Finney写道：
Ben Finney wrote:
我可以请求为了减少混淆，任何
预发布版本的2.5.3（或任何其他的b $ b $ Python版本）的公告都要公布*，而不是*说a ??释放：一个
不是真正发布的Pythona版本??
看到主题公告的进展是非常令人困惑的
字段如：
发布：Python 2.8.not-ready-yet
发布：Python 2.8.alpha-1
发布：Python 2.8.beta-1
发布：Python 2.8.bet a-2
发布：Python 2.8发布候选版本1
发布：Python 2.8发布候选版本2
发布：Python 2.8最终
Can I request, in the interest of reducing confusion, that any
announcements of pre-release versions of 2.5.3 (or any other
Python release) be announced *without* saying a??RELEASED: A
not-really-release version of Pythona??.
It''s very confusing to see a progression of announcements with subject
fields like:
RELEASED: Python 2.8.not-ready-yet
RELEASED: Python 2.8.alpha-1
RELEASED: Python 2.8.beta-1
RELEASED: Python 2.8.beta-2
RELEASED: Python 2.8 release candidate 1
RELEASED: Python 2.8 release candidate 2
RELEASED: Python 2.8 final
我不同意。这些确切地说明了发生了什么并告诉我我想要知道的是什么，这是一个新的东西已经发布，这可以说是可以下载的。
I disagree. These say exactly what has happened and tell me what I
want to know, which is that something new has been released, which is
to say, made available for download.
这与a ?? releasea完全不同？隐含在例如释放候选人的情况下，因此他们没有说出他们的意思。
由于后一个词不太可能改变，我'要求
公告没有不必要地超载释放的含义??
Which is entirely different from the a??releasea?? implicit in e.g.
a??release candidatea??, hence they don''t say what they appear to say.
Since the latter term is unlikely to change, I''m asking that the
announcements don''t unnecessarily overload the meaning of a??releasea??.
我不同意。 [ANN]可能意味着什么：有计划的？取消？需要帮助吗？
（哦，''已发布''，为什么你不这么说？）
I disagree. [ANN] could mean anything: planned? canceled? needs help?
("Oh, ''released'', why didn''t you say so?")
如上所述，释放了?? ??这是一个很糟糕的术语，因为它*已经*已经完成了所有的完成，出门，准备goa ??在发布候选版本中证明了
？ （未发布，但我们认为可能是这样）和
伴随
*实际*发布的胜利公告的区别。
As above, a??releaseda?? is a poor term for this, since it *already* has
connotations of a??all done, out the door, ready to goa?? as evidenced
in a??release candidatea?? (not released, but we think it could be) and
the distinction of the triumphant announcements that accompany
*actual* releases.
我认为你不会对[ANN] Python
xywhatever released表示满意。
I presume you would not be happy either with "[ANN] Python
x.y.whatever released".
我希望很清楚为什么会这样，是的。
I hope it''s clear why that''s so, yes.
（I我目前正在使用3.rc1;剩下的问题目前没有
影响我，我接受风险，我认为这个风险很小，进一步
更改会影响代码我现在写。）
(I am currently using 3.rc1; the remaining problems do not currently
affect me and I accept the risk, which I view as small, that further
changes will affect code I write now.)
注意你使用的是aa ?? release candidatea ??，即一个版本的
软件*没有尚未发布*。它肯定会更清晰
如果该版本的可用性没有宣布该软件已经发布和未发布的
暗示。
Note that you are using a a??release candidatea??, i.e. a version of
software *that has not yet been released*. It would surely be clearer
if the availability of that version were not announced with an
implication that the software is both released and not-released.
如果你想要更换RELEASED，建议简短但不要太多
丑陋的沟通发布在python.org并且可以是
已下载，安装，测试和使用至少也是如此。
If you want RELEASED replaced, suggest something short and not too
ugly that communicates "posted at python.org and available to be
downloaded, installed, tested, and used" at least as well.
我建议?? AVAILABLEa ??，然后，明确限制
州宣布的范围。
无论选择什么，请保留一个?? RELEASEDa ??对于
通常预期的含义类似于......不再是
密集开发或错误搜寻模式，现在已经准备好了它的
拥有并被群众放弃使用??
-
\ a ??随机数的生成是太重要了，不能离开|
` \ to chance.a ?? a ?? Robert R. Coveyou |
_o__）|
Ben Finney
I suggest a??AVAILABLEa??, then, to clearly limit the scope of what
state is being announced.
Whatever is chosen, please reserve a??RELEASEDa?? for the
commonly-expected meaning of something akin to a??no longer in
intensive development or bug-hunting mode, now ready to go out on its
own and be used with abandon by the massesa??.
--
\ a??The generation of random numbers is too important to be left |
`\ to chance.a?? a??Robert R. Coveyou |
_o__) |
Ben Finney
这篇关于Python 2.5.3：调用补丁的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
