So one of the best things about doing things is you learn things, so the next time you do them you’re better at them. We just released OpenSearch 2.0 and we learned a couple of things: 1/ Having a long gap between 2.0 release candidate and 2.0 release makes it weird to build features. We didn’t wa…

+1 to move 3.0 to 2023. Since Segment Replication and Remote Index can be delivered in minor versions, this also will give more time for developers to leverage the new inclusive usages before removing deprecated usages.

I can definitely see both perspectives, but I lean towards a longer time between majors (option 2). This will help users have more time to ramp onto 2.0 and not have to think through potential breaking changes across two major versions. And +1 to @nknize ’s point on not feeling locked on delivering n…

One thing to consider is that OpenSearch Dashboards will need a 3.0 release before April 30th, 2023 in order to upgrade Node.js from v14 to a newer version (v16 or v18) before the end of LTS. Releases | Node.js

I bet we can decouple OpenSearch from OpenSearch Dashboards releases before April 2023. :slight_smile:

I think not considering the elastic compatibility and client issues I link to is a big miss if we don’t consider a 3.0 release sooner than later. Maintainers will be the ones pulling the magic to keep the house of cards standing and users will be the ones continuing to endure pain until they decide …

Another thing to consider. If we release 3.0 in September with Lucene 9.x, the REST Version API, and Elastic 7.x version removal, users can perform a direct 1.x to 3.0 rolling upgrade without having to go to 2.0 first; and client compatibility (including beats and Logstash fixed version compatibilit…

I would prefer we don’t bake too many exciting new features for too long, and thus would prefer an earlier schedule (version 1). My biggest concern is that by extending the schedule we are just deferring assembling 3.0 till later, instead of getting serious about it in parallel with 2.x. The time to…

Personally, I was leaning towards 2nd option before we brought back spoof hacks for compatibility with Elasticsearch clients . Essentially, we still cannot break ties from Elasticsearch as @nknize mentioned, sooner we do that - better it is going to be for both projects and communities. In these re…

+1 to all your comments, especially moving the Remote Index work to 2.x

I am concerned with option 1. It seems like we are doing another major version and introducing breaking changes earlier than we need to for the sake of breaking. I agree with @dblock that we should be assembling 3.0 in parallel with 2.x, but I don’t think we need to push to launch 3.0 early if we ha…

Dates for 3.0.0?

General Feedback

himanshusetia July 19, 2022, 11:25pm 29

FYI Please refer to the poll results for decision on 3.0.0 dates - Poll: 3.0 release

Topic		Replies	Views
FEEDBACK: Finalize 2024 release schedule for OpenSearch Request For Comments discuss	3	456	February 21, 2024
2.0 release date discussion General Feedback releases , discuss	17	1578	March 27, 2022
2022 Release Schedule General Feedback discuss	7	1063	March 18, 2022
OpenSearch 1.x EOL OpenSearch	2	815	July 19, 2023
Seeking feedback on client compatibility across major versions OpenSearch Client Libraries clients-general	2	692	April 26, 2022

Dates for 3.0.0?

Related topics