Add docs for game support, releasing and extensions - #24093
Closed
insomnious wants to merge 1 commit into
Closed
insomnious wants to merge 1 commit into
insomnious wants to merge 1 commit into
Conversation
New engineers start soon and there was nothing to point them at for how a game comes to be supported, or for what happens to a release once it is packaged. Game support and extensions had no docs at all. Releasing had six accurate docs and no map, so that one is mostly links plus the three parts nobody had written down: the post-release automation, signing as an operation, and announcing. The announcing section is reconstructed from Slack rather than from anything in the repo, so it needs confirming with Vitalii and comms before anyone relies on it.
|
This PR has been marked as stale due to inactivity. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three docs for onboarding: how a game comes to be supported, what happens to a release after it is packaged, and what an extension is. Game support and extensions had nothing at all. Releasing had six accurate docs and no map, so that one is mostly links plus the post-release automation, signing operations and announcing.
The announcing section is reconstructed from Slack rather than from the repo, so it needs a check from Vitalii and comms before anyone relies on it.