Proposed changes to minor release process #151
Conversation
CEHENKLE
requested review from
dblock,
mch2,
peternied and
saratvemulapalli
as code owners
CEHENKLE
added
discuss
There was a problem hiding this comment.
+1 on the proposal in #150
I think this significantly duplicates the content in the release template, so I think it belongs in https://github.com/opensearch-project/opensearch-build/blob/main/.github/ISSUE_TEMPLATE/release_template.md
| On release window start date: | ||
| 1. We generate the first candidate with all plug-ins/components that have met the entrance criteria. If a plug-in/component hasn't met all of the criteria, we'll version bump the last released version and release that. Once the release window opens and the first candidate is generated, no additioanl features can be added, and we will not delay the start of a release window for any plug-in/component. | ||
| 1. During the release window we will do final quality testing, documentation and performance testing. Bug fixes can be added in during this time, but no new features will be added. | ||
| 1. We will generate a new candidate every day and post on the release issue about the status of the exit criteria. When all the exit criteria have been met, we'll announce that the candidate is ready and release it 2 days later (unless that falls on Friday, in which case we'll release on Monday) |
There was a problem hiding this comment.
Will the candidate be deployed somewhere publicly on a playground?
There was a problem hiding this comment.
I've opened an issue to request the the nightly build get deployed to playground: https://github.com/opensearch-project/opensearch-build/issues/3881
But we generally put up the RC builds, even if they're not on playground.
Feel free to add to the issue
|
|
||
| #### Entrance criteria to start release window: | ||
| * Documentation draft PRs are up and in tech review for all component changes. | ||
| * Sanity testing is done for all components. |
There was a problem hiding this comment.
I can answer this. Sometimes we do have humans clicking some buttons and call it "sanity testing" :)
There was a problem hiding this comment.
Yup. db is correct. It's very basic "please make sure everything looks sane to a human in case anything is missed by automated testing" testing.
|
per slack discussion should we include the proposed updates to the release calendar in this PR? Specifically moving 2.10 to 9/12, 2.11 to early November, and 2.12 to January '24 |
Signed-off-by: CEHENKLE <henkle@amazon.com>
Signed-off-by: CEHENKLE <henkle@amazon.com>
Signed-off-by: CEHENKLE <henkle@amazon.com>
Signed-off-by: CEHENKLE <henkle@amazon.com>
Signed-off-by: CEHENKLE <henkle@amazon.com>
Signed-off-by: CEHENKLE <henkle@amazon.com>
Signed-off-by: CEHENKLE <henkle@amazon.com>
RELEASING.md
Outdated
|
|
||
| Please note: This process is for regularly scheduled minor and patch releases. For "hot" patches (patches required for security or other urgent issues) we will build, test and release as quickly as possible. | ||
|
|
||
| #### Entrance criteria to start release window |
There was a problem hiding this comment.
This language doesn't 'flow' for me. I don't start a 'time box', I start a doing a completable task or abort when out of time.
There was a problem hiding this comment.
Did you mean to highlight this section? If so, do you have a language suggestion?
Thanks!
There was a problem hiding this comment.
This was the right section, but I don't have a suggestion - if it works for you lets keep it. I can always make a PR if I come up with something clever
CEHENKLE
removed
the
bake-time
Signed-off-by: CEHENKLE <henkle@amazon.com>
There are no dates in this PR. But I've updated the releasing.md to reflect the new dates. |
uppercased. |
|
@CEHENKLE Did you mean to merge without waiting for the bake-time to complete? |
|
I did, since the proposal hasn't substantively changed since it went up in March. I figured that was enough baketime. |
Description
Updated text for proposed change to the minor release process. Please see opensearch-project/opensearch-build#150 for more context
Issues Resolved
opensearch-project/opensearch-build#150
Please do not merge this any earlier than April 14th.
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.