[FEATURE REQUEST] separate repos for LTS and Dev
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Is your feature request related to a problem? Please describe.
When updating the Salt Repo, the LTS version (currently v3006) and the Dev version (currently v3007) are mixed in the same repo. When updated, both repos are pulled. When a deployment is attempted for a minion, the v3007 is deployed. This, however, is not supported by VMware/Broadcom.
Describe the solution you'd like
Would it be possible to separate the versions into 2 separate repositories, one for LTS and one for Development? This would greatly improve the deployment.
Describe alternatives you've considered
manual separation (a pain) or virtual links, but both are negated once an update overwrites.
Additional context
no additional info
Please Note
If this can be fixed in another way, please advise.
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, tests, or entry points are identified in the issue. Start by tracing how Salt LTS and development versions are currently published and selected during deployment, then determine the repository and release changes needed. Done means LTS and development artifacts are separated and deployments can reliably select the supported LTS version.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, infrastructure, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100