Skip to content

Add: Refactoring Requirements doc#371

Merged
Nepiki merged 4 commits into
RetroAchievements:mainfrom
suspect15:refactor
May 25, 2026
Merged

Add: Refactoring Requirements doc#371
Nepiki merged 4 commits into
RetroAchievements:mainfrom
suspect15:refactor

Conversation

@suspect15

Copy link
Copy Markdown
Contributor

Adds a doc that outlines inactive dev set refactoring requirements. This is a draft that will be subject to change after QA discussion.

@suspect15 suspect15 marked this pull request as draft May 22, 2026 23:21
@suspect15 suspect15 marked this pull request as ready for review May 25, 2026 18:52
@suspect15

Copy link
Copy Markdown
Contributor Author

Ready to merge


# Refactoring Overview

Refactoring a set on RetroAchievements is the act of bringing a substandard, inactive developer sets up to modern standards. Ridding the library of poorly noted, coded, and implemented sets is the only way RetroAchievements can attain longterm stability. This doc provides guidance on what is required to bring a set up to modern standards and consider it no longer an instability risk to the project. Once a refactor is completed in accordance with these guidelines, the set can be marked by QA as "refactored" and should be considered stable in perpetuity.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sets => set

@Nepiki Nepiki merged commit 3f0fc6b into RetroAchievements:main May 25, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants