> I always thought that the idea of a release candidate was that if there > were any fixes _at all_ that there would be a new rc. Only when no > bugs needing fixed are found does the rc turn into the actual release. This was also my understanding; that's the point of calling it "candidate". Since the code base of 2.6.4rc1 was not released as-is, we would need to consider another candidate. But then, Barry doesn't like release candidates in the first place. Regards, Martin
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