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

Update release guide to reflect process for releasing from a branch #774

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gkamat
Copy link
Collaborator

@gkamat gkamat commented Mar 1, 2025

Description

Update release guide to reflect process for releasing from a branch.

[Describe how this change was tested]


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

4. Run `opensearch-benchmark --help`
5. Run `opensearch-benchmark list workloads`
6. Run a basic workload on Linux and MacOS: `opensearch-benchmark execute-test --workload pmc --test-mode`
7. If you are aware of a change going into the version being released, you can run `python3 -m site` (assuming you installed the latest version that was just released) and get the path for Python. Visit the `osbenchmark` directory and verify that the change exists in the associated OSB files.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you clarify here? Do you mean you can verify a code change will be going into the next version by directly opening the file and checking for the change?

@OVI3D0
Copy link
Member

OVI3D0 commented Mar 3, 2025

lgtm, just needed clarity on one small part

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

Successfully merging this pull request may close these issues.

2 participants