-
Notifications
You must be signed in to change notification settings - Fork 71
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
Update RELEASING.md #184
Conversation
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. |
There was a problem hiding this comment.
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 ...
There was a problem hiding this comment.
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..
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. |
There was a problem hiding this comment.
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.
@mashah Thanks for opening this pull request, its been several weeks without activity, how can I help? |
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]>
There was a problem hiding this 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.
There was a problem hiding this 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
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.