Figure out Process for Participating in 2.13 Release

[epugh]

No description provided.

[epugh]

This was shared with me as one approach: Aiven-Open/prometheus-exporter-plugin-for-opensearch#251

[epugh]

Set up a call with Barani for Thursday with @jzonthemtn and myself. We'll document what we learn here.

[jzonthemtn]

It will be best for us to participate in the near-future releases as a separate project/repository instead of having the opensearch-ubi repository moved under the opensearch organization. We can make an issue in the OpenSearch project to start this process but it will be a lengthy process.

We can test the plugin on the OpenSearch RC and be ready to release an updated version of the plugin with the release of the new OpenSearch version.

We should rename the project's group ID to be com.o19s and work toward deploying the artifacts to Maven Central as other plugins do. There is an issue #95 for deploying to Maven Central.

We should build out the plugin's CI/CD to have a solid, repeatable build/test/release process to help make new versions easy and successful.

Some issues were written to accomplish these things:

• Look at plugin template to make sure this plugin is in compliance #102
• Change plugin maven group to be for o19s #101
• Find a place to store the JS reference implementation with the plugin zip #104

There is already an issue to further build out the CI/CD - #13

Some useful links for reference related this these topics:

• [RELEASE] Release version 2.12.0 opensearch-project/opensearch-build#4115
• https://github.com/opensearch-project/opensearch-plugin-template-java
• publish releases to maven Aiven-Open/prometheus-exporter-plugin-for-opensearch#64
• https://github.com/opensearch-project/opensearch-build

I'm closing this issue because we know the immediate path forward now to have the plugin available with new OpenSearch versions.