> Is it worth holding 2.3.1 until after Panther ships, on the assumption that > its release will turn up more users and more bugs? If not, 2.3.1's timing > can probably be left up to the release manager, who can make the release > whenever he feels like it. Last month, we worked out a tentantive plan to start the 2.3.1 release process in the third week of September. I think we should stick with that. The initial round of bugfixes is an important step for 2.3 being viewed as stable and to show everyone that development/support has not vanished. If critical bugs surface later, that can be a consideration for 2.3.2. There is no reason to be stingy with the initial bugfix release. Raymond ################################################################# ################################################################# ################################################################# ##### ##### ##### ################################################################# ################################################################# #################################################################
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