elastic / elastic/kibana-load-testing
Create branches based on stack versions
Open
enhancement
- Dominant language
- Scala
- Stars
- 6
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Based on recent updates, it is hard to maintain multiple versions in the same branch.
Following kibana repo should make it way easier.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, entry points, or specific stack versions are named. First clarify which versions need separate branches and the expected branch naming and maintenance workflow, then inspect the repository structure and recent update history; done means the version-branch strategy is documented and agreed upon.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100