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

[PROPOSAL] Document running campaigns #61

Open
dblock opened this issue Oct 6, 2022 · 0 comments
Open

[PROPOSAL] Document running campaigns #61

dblock opened this issue Oct 6, 2022 · 0 comments

Comments

@dblock
Copy link
Member

dblock commented Oct 6, 2022

What/Why

What are you proposing?

We have a concept of campaigns, e.g. campaigns in opensearch-build. Document how those are created/run.

AFAIK that is:

  1. Identify a repo where to run a campaign (e.g. opensearch-clients for all clients, or opensearch-plugins for all plugins).
  2. Create a parent issue in that repo.
  3. Use meta to create child issues in all related repos, linking back to the parent issue by saying "Coming from ..."
  4. Create manual issues in any remaining repos, e.g. OpenSearch for when wanting a change in all plugins and OpenSearch.
  5. Update the parent issue with - [ ] link to each child GH issue, now each child will say "tracked in parent"
  6. Label all issues for a release.

What users have asked for this feature?

Coming from opensearch-project/opensearch-plugins#163 (comment)

What problems are you trying to solve?

Create a standard procedure for making campaigns.

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

No branches or pull requests

1 participant