-
Notifications
You must be signed in to change notification settings - Fork 888
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
Release Version 2.8.0 #4074
Comments
42 tasks
This was referenced May 31, 2023
kavilla
added a commit
to kavilla/OpenSearch-Dashboards-1
that referenced
this issue
Jun 8, 2023
Bump version from 2.8 to 2.9 Issue: opensearch-project#4074 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
kavilla
added a commit
to kavilla/OpenSearch-Dashboards-1
that referenced
this issue
Jun 8, 2023
Bump version from 2.8.0 to 2.8.1 Issue: opensearch-project#4074 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
manasvinibs
pushed a commit
to kavilla/OpenSearch-Dashboards-1
that referenced
this issue
Jun 14, 2023
Bump version from 2.8 to 2.9 Issue: opensearch-project#4074 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
joshuarrrr
pushed a commit
that referenced
this issue
Jun 23, 2023
Bump version from 2.8 to 2.9 Issue: #4074 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
kavilla
added a commit
that referenced
this issue
Jun 27, 2023
Bump version from 2.8.0 to 2.8.1 Issue: #4074 Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a component issue for 2.8.0.
Coming from opensearch-build#3434. Please follow the following checklist.
Please refer to the DATES in that post.
How to use this issue
This Component Release Issue
This issue captures the state of the OpenSearch release, on component/plugin level; its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help.
Any release related work can be linked to this issue or added as comments to create visiblity into the release status.
Release Steps
There are several steps to the release process; these steps are completed as the whole component release and components that are behind present risk to the release. The component owner resolves the tasks in this issue and communicate with the overall release owner to make sure each component are moving along as expected.
Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release. The most current set of dates is on the overall release issue linked at the top of this issue.
The Overall Release Issue
Linked at the top of this issue, the overall release issue captures the state of the entire OpenSearch release including references to this issue, the release owner which is the assignee is responsible for communicating the release status broadly. Please contact them or @mention them on that issue for help.
What should I do if my plugin isn't making any changes?
If including changes in this release, increment the version on
__2.x__
branch to__2.8.0__
for Min/Core, and__2.8.0.0__
for components. Otherwise, keep the version number unchanged for both.Preparation
v2.8.0
.CI/CD
2.8.0
are complete.Pre-Release
2.8
release branch in the distribution manifest.2.8.0
have been merged.Release Testing
Release
Post Release
The text was updated successfully, but these errors were encountered: