Determine policy for build retention
Open
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
In building the new backup server, I ran into an issue where we had several terabytes of old nightly and v8-nightly builds going back 8 years.
Preserving this data has a cost, and I'd like to discuss whether it needs to be preserved moving forward.
Im struggling to come up with a use case for needing to keep nightlies that far back in time. Perhaps this is something that can be addressed at the TSC level?
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
The issue names no files, tests, or implementation entry points. First clarify the retention policy and whether the TSC must decide; done means an agreed policy for preserving or removing old nightly and v8-nightly builds.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100