oxidecomputer / oxidecomputer/quartz
Quartz release process
Open
Nobody has claimed this yet.
build system
enhancement
- Dominant language
- VHDL
- Stars
- 22
- Forks
- 2
- Avg merge
- 9h 38m
- Merged PRs (30d)
- 1
Description
Would like to sort out a process for doing GH releases from quartz that makes sense for both developers and consumers.
Thoughts:
- We ideally only want to build stuff that has changes. This helps keep changes traceable so you can see when revisions bump there were actual changes
- We could consider pulling forward old, non-changed binaries into a "quartz release snapshot" that increments anytime anything inside changes. This could then be consumed by down-stream tooling as needed, and since files would only be updated if there were changes it's "safe" to unpack the whole thing and you'd only get diffs where there were changes
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
No files, tests, or release entry points are named. First map the existing Quartz GitHub release workflow and how changed and unchanged binaries are built and consumed; done means an agreed process that preserves traceable changes and defines the proposed release snapshot behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100