[AUTO] Increment version to 2.15.1-SNAPSHOT

[opensearch-trigger-bot]

• Incremented version to 2.15.1-SNAPSHOT.

[dbwiddis]

@lezzago @qreshi @bowenlan-amzn @rishabhmaurya @getsaurabh02 @eirsep @sbcd90 @AWSHurneyt @engechas @riysaxen-amzn @jowg-amazon

Hi, can you please merge this? It's been open since Jun 25 (17 days). I'm trying to be patient here, but this is a recurring problem so I'm going to keep bringing it up.

I'm trying to clear my PR backlog and close this PR which depends on it.

• [AUTO] Increment version to 2.15.1-SNAPSHOT flow-framework#751

It is also currently blocked by these three PRs which depend on it.

• [AUTO] Increment version to 2.15.1-SNAPSHOT ml-commons#2593
• [AUTO] Increment version to 2.15.1-SNAPSHOT neural-search#807
• [AUTO] Increment version to 2.15.1-SNAPSHOT k-NN#1775

Merging it is part of the 2.15.0 release checklist that has not been addressed for this repo. It does not appear anyone gets assigned to do this as part of releases.

• [RELEASE] Release version 2.15.0 #652

I realize these patch version bumps are rarely used, but when we do decide to cut patch releases they are usually intended to be fast security fixes and having a chain of dependencies like this just adds delays in the process.

Minor version bumps are more important to merge more quickly, as failing to merge them before the next version branch is cut can break autosync automations and require a lot of manual effort to recover from, vs. what's usually a very quick approval of these PRs.

Is there some other means of getting more attention on getting these version bump PRs merged more promptly?

[bowenlan-amzn]

@praveensameneni ^^