Standardize processes across all plugins

[saratvemulapalli]

Here is a meta issue for all plugins to track items which have to be taken care of between RC1 and GA for all the plugins.
Create an issue for the plugin you own and take care of the checklist.

• Plugin branching strategy - Document and standardize release and branching strategy for plugins #35
• Backward compatibility testing - Plugin upgrade path from versions prior to OpenSearch 1.0.0 #39
• DCO checks - Turn on DCO checks for all opensearch plugins opensearch-build#53
• Broken links check - Check broken links automatically  #29
• Standardize labels - Create labels that match OpenSearch for versions in plugin repos #43
• README.md, etc - Level up markdown content in all repos in this organization .github#8
• Release Tags #59
• Release notes #58
• Ensure public documentation for plugins is updated #57
• Clean up branches - Standardize release, branching and labeling process for all org repos  .github#13
• Issue and PR templates - Standardize and monitor organizational issue templates .github#9
• CI workflows #60
• Plugins dependencies from Maven - Use AWS OSS Maven -SNAPSHOT for plugin dependencies #45
• Test coverage reporting - Add test coverage reporting #46
• License header checks - Add automated license header checks  #49
• Plugin artifact names - Standardize plugin artifact names #47
• Branch protection rules - Ensure branch protection rules across all plugin repos #52

[dblock]

I propose we split these into separate issues, and label them for v1.0.0? This way we can track a bunch of things under a label.

Add consistent version labels.

[saratvemulapalli]

I understand the value of having multiple issues and can be tracked using a label. Would it be cumbersome for folks to track all the items to put thoughts into?

[dblock]

I understand the value of having multiple issues and can be tracked using a label. Would it be cumbersome for folks to track all the items to put thoughts into?

I do like having a meta issue, but an issue is an issue is an issue, we probably don't want to mix discussions and PRs

... I don't feel strongly about any of this

[ohltyler]

@saratvemulapalli @dblock another thing - now that Dashboards defaults to kebab-case for installed plugins, shall we finalize naming conventions for the build zips for Dashboards plugins?

Current zip convention: <pluginName>Dashboards-x.zip (e.g., anomalyDetectionDashboards-1.0.0.0-rc1.zip`)

New ideas:
Option 1: identical to existing name, but in kebab-case: <plugin-name>-dashboards-x.zip (e.g., anomaly-detection-dashboards-1.0.0.0-rc1.zip.
Option 2: same convention as OpenSearch plugins, but replacing opensearch with dashboards: dashboards-<plugin-name>-x.zip (e.g., dashboards-anomaly-detection-1.0.0.0-rc1.zip (this was mentioned here as well)

Any thoughts here? I think either make sense. Option 1 will keep consistency with the existing plugin IDs which are following the camelcase convention of <pluginNameDashboards> (note that this could be changed to something like dashboardsPluginName, but will require more code changes & testing). Option 2 will keep consistency with OpenSearch plugin names, in regards to the zips at least.

[dblock]

@ohltyler I opened #47 (you can just open issues next time too!) will add comments there

[anirudha]

Looking ahead, I would like it if these issues were broken down into individual issues. Individual issues so much easier to track

[dblock]

Looking ahead, I would like it if these issues were broken down into individual issues. Individual issues so much easier to track

They are, aren't they?

[anirudha]

I understand the value of having multiple issues and can be tracked using a label. Would it be cumbersome for folks to track all the items to put thoughts into?

I do like having a meta issue, but an issue is an issue is an issue, we probably don't want to mix discussions and PRs

... I don't feel strongly about any of this

we couldnt confirm if everything here was covered as separate issue. I saw a few. So now we had to see this meta issue plus a few others.

No worries, will track only the issues in each repo. thanks!

[dblock]

I'm going to close this, we've done most of it, and original intent was just to collect work up to 1.0 GA.