updating releases page to reflect release windows#1866
updating releases page to reflect release windows#1866krisfreedain merged 9 commits intoopensearch-project:mainfrom
Conversation
…cribing the process 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>
|
@bbarani useful? |
Signed-off-by: CEHENKLE <henkle@amazon.com>
releases.md
Outdated
| For minor version releases, OpenSearch follows "release window" model as described in this [proposal](https://github.com/opensearch-project/.github/issues/150). The goal is to release a new minor version approximately every six weeks which includes all the new features and fixes that are ready to go. Once we enter a release window, every day we will generate a release candidate. When the exit criteria are met by a release candidate, we will make an announcement, update the release date column above and publish new artifacts on that date. | ||
|
|
||
| **Note:** If we cannot pass the exit criteria by 2 weeks after the start of the release cycle window, we will cancel the minor release and hold changes until the next release window. | ||
| **Note:** If we cannot pass the exit criteria by 2 weeks after the start of the release cycle window (1 week for 1.x releases), we will cancel the minor release and hold changes until the next release window. |
There was a problem hiding this comment.
We only do patch release in 1.x line. I assume the updated release process is only valid for minor and patch release will still follow release train model?
There was a problem hiding this comment.
If I updated it to being "1 week for 1.x patch releases", would that be more or less clear?
There was a problem hiding this comment.
Yeah, Patch release still follows release train model so just want to make sure that no one gets confused with updated minor release process.
There was a problem hiding this comment.
okay, updated. Please review, LMK if there are any other changes. Thanks!
krisfreedain
left a comment
There was a problem hiding this comment.
Left a comment on too many deletions. There's a comment from @bbarani in there as well
| | 1.3.11 | June 22nd | June 29th | | ||
| | 2.9.0 | July 11th | July 24th | | ||
| | 1.3.12 | August 3rd | August 10th | | ||
| | 2.10.0 | September 05th | TBD | |
There was a problem hiding this comment.
I don't think we want to delete this history as we move it to a 'Release History' section at the end of the year.
There was a problem hiding this comment.
Okay, I reread your comment, and realized you were right. Sorry! Updated.
Signed-off-by: CEHENKLE <henkle@amazon.com>
Signed-off-by: CEHENKLE <henkle@amazon.com>
Signed-off-by: CEHENKLE <henkle@amazon.com>
|
hold - resolving issues with the table layout |
moved the "<div class="table-styler"></div>" down so the first table displays correctly dropped the '2023' from the first table, it seems unnecessary with this new layout Signed-off-by: Kris Freedain <kris@freedain.com>
|
Minor edits made - LGTM |
As per opensearch-project/project-website#1866 There's a few other wording changes, but they're minor so we can ignore them
As per opensearch-project/project-website#1866. There's a few other wording changes, but they're minor so we can ignore them. Co-authored-by: Marc Wrobel <marc.wrobel@gmail.com> Co-authored-by: BiNZGi <BiNZGi@users.noreply.github.com>
Description
updated release page to reflect opensearch-project/.github#150
Issues Resolved
opensearch-project/.github#150
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.