Well, how about taking a baseline snapshot now and branching the tree (I can almost hear Barry groaning all the way in Chicago...)? If the CNRI stuff gets cleared up quickly, the baseline + bug fixes becomes the 2.0 release and the other branch becomes 2.1 or something later. If it takes several weeks or a month (or more?), the snapshot gets forgotten and the branch becomes 2.0. I know branching is a struggle, probably not helped by the addition of the SourceForge stuff to the mix, but it might work out here. Skip
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