On Wed, Mar 26, 2014 at 11:54 AM, Nikolaus Rath <Nikolaus at rath.org> wrote: > 2. Change the behavior immediately, potentially breaking some > applications that worked around it, but unbreaking others that relied > on the documented behavior. If it's a functionality change that's likely to break code, would it be worth changing it only in 3.5, and documenting it as broken in 3.4 and earlier? ChrisA
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