Create final tag for ccpp-prebuild and freeze/remove the code?
Open
@climbfuji is already working on this.
Since Apr 23, 2026.
capgen-unification
ccpp_prebuild
enhancement
question
- Dominant language
- Python
- Stars
- 25
- Forks
- 67
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
Description
At this point, we are all committed to moving away from ccpp-prebuild.
Solution
We should consider creating a final tag of the current develop branch, adequately named, and then freeze the ccpp-prebuild.py code. At the same time, we should set a date for the removal of the code - or maybe remove it right away. Folks who need to use ccpp-prebuild.py because they are not yet ready to transition to capgen should use the tag.
Alternatives (optional)
Do nothing.
Related to (optional)
capgen unification
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.
Assessment
This issue has not been assessed yet.