So if there turns out to be a major security hole or sever bug in 2.7, then it shouldn't be filed against 2.7? and fixed in a 2.7.x sort of branch? In that case, would you just suggest everyone using 2.7 to jump to 3.x?
As long as a 2.x version is supported, filing bugs, branching and even releasing critical updates is, although rare, a fact of life. On Thu, 23 Sep 2010 19:06:29 -0400, Terry Reedy <tjre...@udel.edu> wrote: > On 9/23/2010 6:17 PM, Nick Coghlan wrote: >> On Fri, Sep 24, 2010 at 5:50 AM, Georg Brandl<g.bra...@gmx.net> wrote: >>>> Setting Versions properly helps anyone searching for issues relevant to >>>> a particular version. If having a field set properly does not matter, >>>> then is should not be there. Are you suggesting that Versions be >>>> deleted? >>> >>> ISTM that the "versions" field is not very useful if the other fields >>> are >>> filled accurately. >> >> It's useful for bug reports to flag affected versions. We should >> probably just *not set it* for feature requests, though. > > Now that 2.7 is out, so that feature requests can only be for a future > 3.x, I would actually like the tracker to restrict the allowed values > for non-doc feature requests either to 3.2/3.3 or to Not Applicable or > whatever. It is a nuisance that people can still file such for 2.7, for > instance. _______________________________________________ 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
