oxidecomputer / oxidecomputer/helios
quick build vs. non-quick version numbers
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 481
- Forks
- 21
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 2
Description
Going through the docs here there's an emphasis on the quick build and the difference in version numbers. When doing development I want all the compilers and lint active to try and catch my issues. This means using the 'illumos.sh' and not 'quick-illumos.sh' files. However, this ends up leading to version numbers that don't match the quick build and perhaps isn't the right path forward.
I guess I'd like to get your take on what version numbers should be when working on multiple different helios projects and switching a target machine between them a bunch.
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.
Research direction
Start by reading the documentation referenced in the issue and comparing illumos.sh with quick-illumos.sh. Trace how each build determines its version number, then establish and document a consistent versioning policy for switching among Helios projects and target machines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, shell
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100