Publish an updated binary release
- Dominant language
- JavaScript
- Stars
- 211
- Forks
- 36
- Avg merge
- 6h 49m
- Merged PRs (30d)
- 1
Description
### What is the problem or limitation you are having?
It has been several years since a formal Podium release has been published. The v0.2 release no longer starts reliably on Linux or macOS.
### Describe the solution you'd like
A formal v0.3 release is required, incorporating the many fixes that have been made
### Describe alternatives you've considered
Continue to rely on users to build from source.
### Additional context
It would be worth using this as an example for how to automate CI generation of release artefacts (see beeware/briefcase#400).
Contributor guide
Research direction
Start by reviewing how the repository currently builds and publishes binaries, then compare the fixes made since v0.2 with the Linux and macOS startup problems. Use beeware/briefcase#400 as the referenced example for CI-generated release artifacts. Done means a formal v0.3 release is published and the binaries start reliably on both platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100