docs: update CONTRIBUTING backporting expectations to reflect reality
Open
Beginner friendly
Nobody has claimed this yet.
documentation
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Package Name
tree-wide
Maintainer
@BKPepe @hnyman @GeorgeSapkin
OpenWrt Version
24.10
Steps to Reproduce
Commits currently are being directly cherry-picked from master to 24.10
Actual Behaviour
I believe, in general, cherry-picks for 24.10 should come from 25.12.
Confirmation Checklist
- The package is maintained in this repository.
- I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
- I am reporting an issue for OpenWrt, not an unsupported fork.
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
Open CONTRIBUTING.md and find the guidance about backporting or cherry-picking packages to the 24.10 branch. Compare it with the reported practice of cherry-picking directly from master and the stated expectation that picks should come from 25.12. Done means the documented expectations accurately describe the current backporting process.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100