> Maybe I should start using the release branch for Mac releases after you are > done with it for the Unix/Windows release. As there is an r22b1 tag to point > to the exact revision used for the release there should be no adverse > consequences. What do you think? As before, I think there should be only a single 2.2b1 release. If you need to provide binaries, use what was released in the 2.2b1 source distribution (which is *not* the Unix release, it is the source distribution). What do your users lose if they have to get 2.2b1 as-is (ie. without further patches)? It may have bugs, sure - but so does the 2.2b1 release for everybody else. There will be a 2.2b2 release, so whatever you commit now will appear in 2.2b2. I think these release schedules are there for a purpose. 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