We discussed this in the last dev meeting. With this issue I want to make it official and summarize our discussion.
Lately Wasabi is getting less and less user friendly https://github.com/zkSNACKs/WalletWasabi/issues/1369 and more and more buggy. Once in a while we have to take a step back and fix up stuff before we start new adventures and this is that time. We have to sort out a couple of things, because the maintenance of this software is getting unbearable.
The requirement to end this feature freeze is that to @lontivero @molnard @danwalmsley or me have to suggest it under this issue. Everyone have a veto and when we all agree to end this feature freeze, we can progress further with new things.
@lontivero have suggested closing this issue. I ACK it. @danwalmsley @molnard ?
Fine
What if we tag master, test it intensively and if everything works okay then we close this issue and release the tagged version?
Ok, so it's basically becomes the same issue as this: https://github.com/zkSNACKs/WalletWasabi/issues/1664
I agree with @lontivero, my only concern is that someone came back and said they still had issue with black screen on linux... https://github.com/zkSNACKs/WalletWasabi/issues/1537#issuecomment-506861009
@nopara73 i think I can fix this https://github.com/zkSNACKs/WalletWasabi/pull/1656 tonight and we can get this in the release, as it will be an easy fix, and it does fix a few annoying layout issues.
@nopara73 i think I can fix this #1656 tonight and we can get this in the release, as it will be an easy fix, and it does fix a few annoying layout issues.
ACK.
I agree with @lontivero, my only concern is that someone came back and said they still had issue with black screen on linux... #1537 (comment)
I have the "spent" issue in my wallet file that wasn't corrected by my algo so I also want to investigate that.
Dan, that's a worrisome issue, but that's a different one from the black screen:
I'm at the current master commit and the window closes for me as soon as I move the mouse or the window loses focus.
Due to the spectacular failure of testing before release and because the spent issues are still present I withdraw my ACK from closing this issue after the release.
We don't keep ourselves to it anymore, so this issue makes no sense at this point.
Most helpful comment
What if we tag master, test it intensively and if everything works okay then we close this issue and release the tagged version?