You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The team should decide a tech lead and a content lead
Content (especially the CHANGELOG/Release notes) needs to be complete before the release process begins
A code freeze timeline should be set (3pm the day before release until release has happened, maybe?)
The tech lead should check the npm access token. If it has expired, or is set to expire within a month, they should rotate it.
We may also want to add some changes to what happens after a release, or document a release timeline so folks don't waste their time by ending up just sitting around watching others and can join when they'll be helpful.
The text was updated successfully, but these errors were encountered:
What
We'll want to tweak what happens before we publish a release and update the documentation.
Some specific changes that might need doing:
We may also want to add some changes to what happens after a release, or document a release timeline so folks don't waste their time by ending up just sitting around watching others and can join when they'll be helpful.
The text was updated successfully, but these errors were encountered: