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 RELEASING.md #184

Merged
merged 5 commits into from
Sep 5, 2024
Merged

Update RELEASING.md #184

merged 5 commits into from
Sep 5, 2024

Conversation

mashah
Copy link
Contributor

@mashah mashah commented Jan 24, 2024

Proposed an update to create a process with involvement from the leadership committee for moving the release date.

Description

See above.

Issues Resolved

See above.

Proposed an update to create a process for moving the release date.

Signed-off-by: Mehul A. Shah <[email protected]>
performance, reliability, availability, or security. In order to move a release date, we will ensure:

* There is a publicly documented justification for moving the release date.
* The justification is circulated 2 weeks or more prior to the original release date.
Copy link
Member

Choose a reason for hiding this comment

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

is posted no later than 2 weeks ...

Copy link
Member

Choose a reason for hiding this comment

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

Can we elaborate on documented justification? Is it GitHub issue in specific repo, Slack or something else..

@Pallavi-AWS
Copy link
Member

Thanks for initiating this thread @mashah. Agree with LC review, however, primary drivers on date pushout will be a vote from maintainers and the infrastructure/release team that manages the release as they are aware of the technical challenges/last minute issues that might have led to a release delay. We need to still work through voting on github, but need to give enough time for stakeholders to review the proposed change


* There is a publicly documented justification for moving the release date.
* The justification is circulated 2 weeks or more prior to the original release date.
* The organization coordinating the release is in favor of moving the release date.
Copy link
Contributor

Choose a reason for hiding this comment

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

might be a nitpick: If the maintainers/release owners are in favor, is that enough? Something about the word "organization" here seems a little funny.

@peternied
Copy link
Member

@mashah Thanks for opening this pull request, its been several weeks without activity, how can I help?

mashah added 4 commits July 9, 2024 08:10
Added:

- Release Process for OpenSearch Major Releases
- Release Process for Changing Release Date

to the table of contents


Signed-off-by: Mehul A. Shah <[email protected]>
Reorganized TOC and shortened release section titles

Signed-off-by: Mehul A. Shah <[email protected]>
Copy link
Member

@dblock dblock left a comment

Choose a reason for hiding this comment

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

I'm good with these changes.

Since .github is about all products in the org, I think we should take out specifics about the OpenSearch distribution from this document (I don't know where, maybe opensearch-build? @getsaurabh02 fyi), but we can do it in another iteration.

Copy link
Member

@peternied peternied left a comment

Choose a reason for hiding this comment

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

Lets merge this - its an improvement that we can iterate on. Thanks @mashah

@peternied peternied merged commit df9cbc7 into opensearch-project:main Sep 5, 2024
3 checks passed
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.

6 participants