Skip to content
This repository has been archived by the owner on Oct 7, 2022. It is now read-only.

Standardize branching to match OpenSearch #36

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

Standardize branching to match OpenSearch #36

dblock opened this issue Jun 22, 2021 · 0 comments
Assignees
Labels

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.
  3. If you are using a develop branch, stop. You should be using the default main brach for furthermost, future development.
  4. Delete any merged/stale/develop/feature branches that are no longer in use.
  5. Communicate any changes in process to your team.

Refer to release branching for more information.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants