Martin von Loewis writes: > One open issue would be to come up with a release schedule. Should > you restrict yourself to patches that also appear in 2.2 (perhaps in > a back-ported fashion), or will you give a deadline for new patches Since the point of a strictly bug-fix release is to fix bugs, I would not tie the 2.1.2 release to 2.2 in any way. The 2.2 developments remain a cheap source of bug fixes, though, so anything that was an actual bug fix should be considered for 2.1.2. If an alternate fix is needed because the codebase changed too much (which may be very possible this time), a completely new patch may be needed. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4