Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up warnings and resolved issues #5199

Merged
merged 1 commit into from
Sep 10, 2024

Conversation

Allofich
Copy link
Contributor

@Allofich Allofich commented Sep 7, 2024

Add a summary of the change(s) brought by this PR here.

What issue(s) does this PR address?

The project has a lot of compile warnings (especially -Wsuggest-override warnings in cdrom.h appear frequently) and there are many resolved-yet-open issues.
Through merging this PR, you can close these issues, which appear to have been resolved:
Closes #1746.
Closes #4977.
Closes #4398.
Closes #2826.
Closes #3345.
Closes #2829.
Closes #2733.
Closes #2869.
Closes #3451.
Closes #4209. (Consensus seems to have been that the problem was not in DOSBox-X)
Closes #2663.
Closes #2787.
Closes #2252. (I don't completely understand this issue from a quick read but there seems to be consensus that the problem was not in DOSBox-X)
Closes #3016.
Closes #1285.
Closes #1822.
Closes #5069.
Closes #3979.
Closes #835.
Closes #1780.
Closes #2589.
Closes #886.

Does this PR introduce new feature(s)?

No.

Does this PR introduce any breaking change(s)?

No.

There is also the question of how to handle all the "Question"-tagged issues in the Issues page. For example in #3483, @maron2000 suggests closing the issue (a "Question" issue) because it had been answered. We could do that, or convert them to Discussions (see https://docs.github.com/en/discussions/managing-discussions-for-your-community/managing-discussions#converting-issues-based-on-labels). We could also leave them as they are, but I feel they are cluttering the Issues page.

@Allofich Allofich changed the title Clean up warnings and stale issues Clean up warnings and resolved issues Sep 7, 2024
@Allofich
Copy link
Contributor Author

Allofich commented Sep 7, 2024

Let's also close duplicate issues.

Closes #4710.
Closes #4997.
Closes #1382.
Closes #2958.
Closes #3532.
Closes #3403.
Closes #2810.
Closes #4527.
Closes #2811.
Closes #2801.
Closes #3356.
Closes #3000.
Closes #2630.
Closes #1825.
Closes #1764.
Closes #4717.

@Allofich
Copy link
Contributor Author

Allofich commented Sep 7, 2024

We should also probably close old issues about build failures, as they become less relevant as time passes and the codebase changes.

Closes #2886.
Closes #275.
Closes #169.
Closes #270.
Closes #265.
Closes #209.
Closes #840.
Closes #925.
Closes #1392.
Closes #1386.
Closes #1512.
Closes #1747.
Closes #2614.
Closes #2605.

@Allofich
Copy link
Contributor Author

Allofich commented Sep 7, 2024

I think issues where there is a likely explanation offered by testers that have looked into the issue that is not the fault of DOSBox-X and the original reporter isn't responding are also fair game for closing. They can always be re-opened if it turns out there actually is a problem.

Closes #4747.

@Allofich
Copy link
Contributor Author

Allofich commented Sep 7, 2024

There are also old "documentation" tagged issues buried in the issues page. Those should probably be moved to the wiki or converted to discussions or something.

@Allofich
Copy link
Contributor Author

Allofich commented Sep 7, 2024

Let's also close any unworkable issues:
Closes #2610.

@joncampbell123 joncampbell123 merged commit 258f2bd into joncampbell123:master Sep 10, 2024
20 checks passed
@Allofich Allofich deleted the tidy branch September 10, 2024 06:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment