Closed leoj3n closed 10 months ago
I would recommend mentioning the beta release link in the README
There is a reason why those versions are marked as beta. They contain known bugs, that are equally bad. (As an example, you currently cannot leave the app while downloading/uploading files, without the transfers beeing stopped.)
I consider regressions to be worse than known bugs, so the 2.2.2/2.2.3 is infact, the latest release. Just because i have fixed some bugs in the current master does not mean it is ready to be advertised or for production usage.
I understand what you mean, I was more suggesting you could add a note like what you are saying here about not using "for production", just maybe a note to check out the beta first to see if the issue has been resolved there.
I just had trouble finding the beta release when using GitHub on my phone so thought you could make it more obvious for someone wanting to try it out.
It's been a while since I've used the GitHub website. I was looking for a "Releases" tab but finally figured out clicking "Tags" for the repository is the only way afaict to get to the Releases page...
I'll assume most everyone else that might submit an issue has figured that out eh... not so intuitive though.
@newhinton
I would be willing to try and get #210 #211 #212 solved in the current "latest" release (I assume I can figure out the config/display issues at least by looking at the beta where they have been resolved) but I'm not familiar with how to build/run the project. Is there any resource you can point me to that would help me understand what I would need to do to develop the app on a Mac? Is it pretty straightforward?
The Wiki contains a section for setting up your developer-environment. The instructions should be OS-agnostic, so they will likely also apply to MacOS aswell.
You are more than welcome to fix those issues for yourself, but it will be very unlikely that i will make another 2.2.x release for them. I am already working on a 2.4 release, so i wont spent much time to fix "older" versions, unless security issues like terrapin show up. (Backporting is not as straitforward than "just" creating a new release, and i was not prepared to do so for terrapin.)
If you want my advice: Check the commit history (https://github.com/newhinton/extRact/compare/v2.2.2...v2.4.3-beta) and try to find the specific changes for the issues you want to backport.
I didn't notice that 2.2.3-terrapin wasn't actually the latest code available. The terrapin release has issues that make it unusable depending on what you're trying to do in the app.
Now that I found the beta release is available all the issues I was having and reported are gone away...
So for anyone else having issues I recommend trying the latest Round Sync Beta release which can be found at the less specific release link than provided by the README.
README release link:
https://github.com/newhinton/Round-Sync/releases/latest
ALL releases link:
https://github.com/newhinton/Round-Sync/releases
Current beta release is RoundSync - v2.4.3-beta
I would recommend mentioning the beta release link in the README as long as the "latest" release is a broken as it is.