Versioning Strategy for Integration Studio and Connector docs
Open
Nobody has claimed this yet.
API-M-4.0.0
Docs/TW
Type/Improvement
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Since the Integration Studio and Connectors are applicable to multiple product versions. Need to revisit the strategy for versioning.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the Integration Studio and Connector documentation and how they currently address multiple product versions. Clarify the versioning strategy and scope with maintainers, then document the agreed approach consistently across both areas.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100