opensearch-project / opensearch-project/opensearch-plugin-template-java
[Discuss] Versioning strategy
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 33
- Forks
- 32
- Avg merge
- 2h 19m
- Merged PRs (30d)
- 3
Description
OpenSearch plugins are attempting to version independently from core OpenSearch but also support a "npm" or "ruby gem" like dependency versioning approach. This issue is intended to capture discussion around how that's supported in the template and what kind of "scaffolding" might help make this easier for the plugin repositories.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reviewing the OpenSearch plugin template and the existing three-comment discussion, then identify how independent plugin versioning and dependency handling are currently represented. Done means an agreed versioning strategy and a defined list of template scaffolding requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100