manifoldco / manifoldco/torus-cli
Automate releasing the msi installer
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 603
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Related #334
We now build the msi installer on each pull request through appveyor. However we have no release process for building, packaging, and releasing the msi installer to users. Ideally, this is done when we release an `rc` or a full version of the cli when a tag is triggered.
Some thought is required on how to manage releases in general considering so whatever we do here is in line with #73.
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 reading related issues #334 and #73, then inspect the existing AppVeyor pull-request build and how release tags are handled. Done means defining and implementing a release process that builds, packages, and publishes the MSI installer for rc and full CLI versions without conflicting with the general release plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100