OpenSearch Release Process #3635
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3635 +/- ##
==========================================
+ Coverage 91.61% 91.86% +0.25%
==========================================
Files 182 186 +4
Lines 5439 5633 +194
==========================================
+ Hits 4983 5175 +192
- Misses 456 458 +2 |
prudhvigodithi
force-pushed
the
public
branch
8 times, most recently
from
4416f13
to
3f700f0
Compare
|
|
||
|
|
||
| #### Windows Integ Test | ||
|
|
There was a problem hiding this comment.
Again, we need to elaborate the steps to setup an instance, test and record the results.
There was a problem hiding this comment.
Adding @jordarlu, jeff you have the detailed steps, can you add them here I will take them as reference?
There was a problem hiding this comment.
sure thing, @prudhvigodithi , let me upadte you on that ... thanks!
There was a problem hiding this comment.
@jordarlu when you get chance can you please share the steps for windows testing?
There was a problem hiding this comment.
Thanks @prudhvigodithi for creating this draft.
Although it is very details I find it overwhelming even as a seasoned release manager.
Wonder if we can simplify the languages and terms a bit. Thanks!
RELEASE_PROCESS_OPENSEARCH.md
Outdated
| #### Integ Test RPM: | ||
|
|
||
| | Integ Test RPM | x64 | arm64 | | ||
| |----------|----------|----------| | ||
| | OpenSearch | [x64](https://build.ci.opensearch.org/job/integ-test/4908/console) | [arm64](https://build.ci.opensearch.org/job/integ-test/4907/console) | | ||
| | OpenSearch Dashboards | [x64](https://build.ci.opensearch.org/job/integ-test-opensearch-dashboards/3532/console) | [arm64](https://build.ci.opensearch.org/job/integ-test-opensearch-dashboards/3533/console) | |
There was a problem hiding this comment.
We can ignore the rpm ones for now as the tar is enough at this stage.
Rpm is similar to tar and deb is having a small bug at the moment.
There was a problem hiding this comment.
Sure Peter, we should still mention, we might get some contributions/fixes from external RM's. WDYT?
RELEASE_PROCESS_OPENSEARCH.md
Outdated
| #### Release Manager | ||
|
|
||
| The release managers to a specific OpenSearch release will be assigned through volunteer model. The request for release managers will be posted in [OpenSearch public slack workspace](https://opensearch.slack.com/archives/C0561HRK961) (under releases channel) and selected on first come first served (FCFS) model. | ||
| Note: The release managers should be maintainers of a repo under OpenSearch GitHub organization. |
There was a problem hiding this comment.
There are release manager and repo owner, which is a bit confusing to people.
Probably the release manager specifically refer to the Primary release manager.
Then component owner might be better than repository owner? Just a thought.
prudhvigodithi
force-pushed
the
public
branch
9 times, most recently
from
940442a
to
cc4cee1
Compare
prudhvigodithi
force-pushed
the
public
branch
4 times, most recently
from
4e73cfb
to
3161130
Compare
There was a problem hiding this comment.
Some good stuff here but I think we need to simplify. I've left some inline comments for things that are confusing to me (let alone a first time RM).
Can we simplify this to an ordered enumerated list of steps to follow? e.g., 1. Release Manager, 2. Feature Freeze, 3. Build RC, 4. Test RC.
Keep it simple, simple, simple. Where the tooling is complex, simplify the documentation. Lets strive for a n00b RM to never have to ask for infra or devops help. Lets keep the fleet of participants as lean as possible.
|
Thanks for the feedback @nknize. |
Signed-off-by: Zelin Hao <[email protected]> Signed-off-by: Prudhvi Godithi <[email protected]>
Signed-off-by: opensearch-ci <[email protected]> Signed-off-by: Prudhvi Godithi <[email protected]>
Signed-off-by: Prudhvi Godithi <[email protected]>
…bIssue` to post:always (opensearch-project#3828) Signed-off-by: Prudhvi Godithi <[email protected]>
…pensearch-project#3829) Signed-off-by: Prudhvi Godithi <[email protected]>
Signed-off-by: Prudhvi Godithi <[email protected]>
prudhvigodithi
force-pushed
the
public
branch
2 times, most recently
from
d10e711
to
4628306
Compare
|
Thanks @dblock updated with your suggestions in latest commit. |
|
Sample created release issue with the latest template: |
prudhvigodithi
force-pushed
the
public
branch
3 times, most recently
from
ce60715
to
ba485d4
Compare
Signed-off-by: Prudhvi Godithi <[email protected]>
|
Thanks everyone for the review and feedback, I will proceed to merge this PR as it is already useful with the release information for an external manager. We can keep improving this document as we move forward with the release retro meetings (Example: https://github.com/orgs/opensearch-project/projects/140/views/1). |
prudhvigodithi
dismissed
nknize’s stale review
Hey Nick, I will be moving forward with this PR, please check my latest comment #3635 (comment). Thanks
Description
Add a detailed document regarding the OpenSearch Release Process.
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
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.