Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require waiting period before publishing a release #34

Open
achrinza opened this issue May 11, 2022 · 2 comments
Open

Require waiting period before publishing a release #34

achrinza opened this issue May 11, 2022 · 2 comments

Comments

@achrinza
Copy link
Member

achrinza commented May 11, 2022

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.

@dhmlau
Copy link
Member

dhmlau commented May 11, 2022

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.

@achrinza
Copy link
Member Author

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.

@achrinza achrinza moved this from Icebox to Current/Backlog in LoopBack Common Project Board May 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Current/Backlog
Development

No branches or pull requests

2 participants