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

Adopt Release Branch Strategy #236

Open
4 tasks
IfSentient opened this issue Mar 28, 2024 · 0 comments
Open
4 tasks

Adopt Release Branch Strategy #236

IfSentient opened this issue Mar 28, 2024 · 0 comments

Comments

@IfSentient
Copy link
Contributor

Currently, the grafana-app-sdk releases from main and has commit-based tags. This prevents us from easily offering continued support for older releases. We should investigate moving toward release branches for each minor release (while still pre-1.0). To do so, we will need to ensure the following:

  • The release script(s) work with release branches instead of main (either cutting a new one for a minor version bump, or using an existing one for a patch)
  • PR's into release branches follow the same rules as PRs into main
  • Dependabot can cut dependency upgrade PRs into active release branches as well as main (otherwise backporting dependency upgrades becomes higher-toil work)
  • The release process needs better documentation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants