"A.M. Kuchling" <a...@amk.ca> writes: > FYI: I've just added the text below to the "What's New" document for > 2.7. I wanted to describe how 2.7 will probably be maintained, but > didn't want to write anything that sounded like an iron-clad guarantee > of a maintenance timespan. Does this text seem like a reasonable set > of statements?
If you give an actual time period, that's all that will actually be communicated to most people. This text will be read by a few people, and communicated as simply “six years” to everyone else. It doesn't matter how many caveats and qualifiers you surround that with; those will all be lost in transmission from person to person. Would it make more sense to, instead of giving a time period, rather describe the *circumstances* that will determine when maintenance releases will cease for 2.7? -- \ “Religious faith is the one species of human ignorance that | `\ will not admit of even the *possibility* of correction.” —Sam | _o__) Harris, _The End of Faith_, 2004 | Ben Finney _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
