![]() ![]() Note: If we cannot pass the exit criteria by 2 weeks after the start of the release cycle window (1 week for 1.x patch releases), we will cancel the minor release and hold changes until the next release window. 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. Once we enter a release window, every day we will generate a release candidate. 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. For example, 1.2.0 will work with 1.3.2, 1.4.1, etc, but may not work with 2.0.įor minor version releases, OpenSearch follows “release window” model as described in our releasing documentation. All minor versions are compatible with every other minor version for that major. OpenSearch follows semver, which means we will only release breaking changes in major versions. Latest Possible Release Date (release window closes) Release Numberįirst RC Generated (release window opens) See below for criteria for a major releases. If/when we add one, it will replace a minor release in the 2.x line. Note: We have not added a major release to the 2024 schedule yet. ![]() For more information on the changes planned for each release, please see the Project Roadmap ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |