Closed macohen closed 6 months ago
- [ ] #17
- [ ] create 2.7 branch
- [ ] create 2.7 release
- [ ] create 2.8 branch
- [ ] create 2.8 release
This should result in a self install plugin for each version of OpenSearch.
I'm closing this in favor of individual issues for each release.
What/Why
This repository contains a Learning-to-Rank plugin forked by @gsingers from the original ElasticSearch plugin built by OpenSource Connections. Our plan is to incorporate the plugin into the OpenSearch build process. This will include changes to the branching strategy to match the OpenSearch build process, building branches for each release since 2.5 (the last release this plugin was compatible with), and pausing when we have a buildable self-install plugin. We do want to take a community vote on including this plugin in the release itself so all work will be in this repo to start.
What are you proposing?
The pattern for most OpenSearch projects in terms of branching is:
I see that some of the mechanisms for cutting a new release will need to change (release.yml, docker.yml). We also want to remove direct dependencies on libraries in the repo.
@gsingers what challenges do you see here from the way the build works?
Update I'm revising this to start with a 2.9 plugin release for a self-install plugin. We'll work on incrementing for 2.10 and 2.11, then take a call on if this plugin should continue to be self-install or included in the release, targeting 2.12 for that.