chore(docs): Add "New SDK Release Checklist" from Notion #6200
Conversation
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
Lms24
force-pushed
the
lms-release-checklist
branch
from
29226cd to
17c9519
Compare
mydea
approved these changes
Nov 14, 2022
Member
mydea
left a comment
mydea
left a comment
There was a problem hiding this comment.
nice, great work! We can then also, piece by piece, start to add more docs there. E.g. a good contender is to move the "release" docs generally into a standalone doc etc., but that's for the future. 🚀
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Following up on a recent incident we had when releasing the Node OTEL package, we decided to port the release checklist for first-time releases of new SDKs from Notion to our SDK repo directly. This PR does exactly that.
I opted to put it under a
docsfolder as we recently discussed that we might want to split large docs (e.g. migration guide) up in the future. Generally, I think it makes sense to have a docs folder.ref: https://getsentry.atlassian.net/browse/WEB-980