Aahz wrote: > As soon as the new version is released, if there is no bugfix planned > for that issue. Two versions later (i.e. 2.3 in this case) even if it > looks like it ought to be fixed in 2.1 -- we haven't been doing bugfixes > more than one version old. That's not to say that if someone wants to cut a 2.2.4 or 2.1.4 I'm going to stop them. I've no interest in maintaining more than trunk plus the most recent maint branch. As for the original query, about what to do with bugs filed against 2.1.x - I'd suggest closing them. There's a vanishingly small chance that there will ever be another 2.1 or 2.2 release. Anthony
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