SAP / SAP/code-pal-for-abap-cloud
Strategy for the 7.58 branch
Open
Nobody has claimed this yet.
- Dominant language
- ABAP
- Stars
- 55
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Dear SAP, what's the strategy regarding the branch SAP_BASIS-7.58-compatible? How do you expect contributions to main to reach the branch? How do you expect contributions to it to reach main? I also noticed the branch only has 9 ATC checks so far and hasn't been updated for two years.
Please explain - thank you 🙂
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
Review the relationship between main and SAP_BASIS-7.58-compatible, including the branch's update history and its nine ATC checks. Done means documenting the expected direction of contributions between the branches and clarifying whether the branch is still maintained.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100