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
Currently, there's no requirement to wait for input from the other TSC members or maintainers before publishing a new release.
This can be problematic as there may be outstanding tasks that need to be settled before making the release. The waiting period will allow TSC members and maintainers to defer a release if needed and to prepare for the release.
A suggestion is to give a 48 hour notice.
The text was updated successfully, but these errors were encountered:
For the connector or not "loopback-next" repo, I wonder if we want to make it be min 24 hours instead. We don't have a regular release schedule in those repos normally. Sometimes when a user reminds us to publish a release, we might want to do it right away before we forget.
I'm ok with 24 hours for loopback-connector* Git Repositories.
Another thing we might want to document is how the notification is sent.
For the sake of transparency and to avoid Slack's 10k message limit, we could require that the notification is a loopback-governance issue with a release-notification tag.
If needed, we can add a GitHub Action workflow to send a Slack notification to #loopback-maintainers as well for higher visibility.
Currently, there's no requirement to wait for input from the other TSC members or maintainers before publishing a new release.
This can be problematic as there may be outstanding tasks that need to be settled before making the release. The waiting period will allow TSC members and maintainers to defer a release if needed and to prepare for the release.
A suggestion is to give a 48 hour notice.
The text was updated successfully, but these errors were encountered: