Skip to content
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 1.1.1 #161

Closed
16 tasks
peterzhuamazon opened this issue Dec 7, 2021 · 0 comments
Closed
16 tasks

Release version 1.1.1 #161

peterzhuamazon opened this issue Dec 7, 2021 · 0 comments

Comments

@peterzhuamazon
Copy link
Member

peterzhuamazon commented Dec 7, 2021

This is a component issue for release 1.1.1.
Coming from release issue 1.1.1, release version 1.1.1. Please follow the following checklist.

How to use this component issue

This Component Issue

This component issue captures the state of the OpenSearch release, on component/plugin level, its assignee is responsible for driving the release of the component. Please contact them or @mention them on this issue for help.

Release Steps

There are several steps to the release process, components that are behind present risk to the release. Component owners resolve tasks on this ticket to communicate with the overall release owner.

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.

You can find all the corresponding dates of each step in the release issue above.

What should I do if my plugin isn't making any changes?

If including changes in this release, increment the version on 1.1 branch to 1.1.1 for Min/Core, and 1.1.1.0 for components. Otherwise, keep the version number unchanged for both.

You can find all the date in above issue

Preparation

  • Assign this issue to a release owner.
  • All the tasks in this issue have been reviewed by the release owner.
  • Create, update, triage and label all features and issues targeted for this release with v1.1.1.

CI/CD

  • All code changes for 1.1.1 are complete.
  • Ensure working and passing CI.

Pre-Release

  • Confirm that all changes for 1.1.1 have been merged.
  • Complete integration and sanity tests, and update results in the comment, example.
  • Find/fix bugs using latest tarball and docker image provided in meta issue.
  • Completed release candidate testing build #TBD.
  • All intermittent test failures have issues filed.

Release

  • Complete documentation.
  • Gather, review and publish release notes.
  • Verify all issued labeled for this release are closed or labelled for the next release.

Post Release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants