Dealing with package rot
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 258
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
We have packages that either no longer build, accidentally broke due to changes in mason itself, or never should have worked because of buggy script.sh usage.
Going to use this ticket to hang ideas for dealing with this. Currently:
- Look at s3 logs for usage of packages. Delete/cull any that are not in use within last month
- Look for problems and fix the rest so they build.
- System to test that all current packages build (travis won't work for this since our triggered API is rate limited at 10 builds and building everything at once would timeout so we'd need to launch a separate build farm).
- Write Mason v2 that supports each project building and publishing packages to fully dodge this issue of maintaining old versions.
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
Start by reviewing the package usage in S3 logs, the existing script.sh usage, and the Travis triggered-build API limits described in the issue. Compare the proposed culling, package build testing, separate build farm, and Mason v2 publishing approaches; the work is done when one approach is scoped and implemented to prevent or address unbuildable packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100