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

Standardize branching to match OpenSearch #33

Closed
dblock opened this issue Jun 22, 2021 · 0 comments
Closed

Standardize branching to match OpenSearch #33

dblock opened this issue Jun 22, 2021 · 0 comments
Labels
enhancement New feature or request v1.0.0

Comments

@dblock
Copy link
Member

dblock commented Jun 22, 2021

Coming from .github#13, standardize release branching to match what OpenSearch is doing.

  1. Create a 1.0 branch for the OpenSearch 1.0 release, 1.x branch for next 1.1 release, and use main for 2.0 development. Make sure CI is enabled on those.
  2. Update your release/branching documentation. If you don't have one, add a RELEASING.md that links to, or has content from .github/RELEASING.md. I did this in Cleanup READMEs. #32
  3. Delete any merged/stale/develop/feature branches that are no longer in use.
  4. Communicate any changes in process to your team.

Refer to release branching for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request v1.0.0
Projects
None yet
Development

No branches or pull requests

2 participants