We should start creating releases on GitHub
- Dominant language
- Java
- Stars
- 287
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
There were a few changes that happened right during the build window and it might be possible that the Windows installer has some fixes/changes that the Linux installation does not. GitHub does allow for defining releases at a specific commit; it might be a good idea to start using that to ensure the Windows and Linux installers are consistent.
This also effectively snapshots a point in time when something was working and is now broken due to multiple seemingly unrelated factors. One could argue this is what commits are for, but if we know what release has it working and what release breaks it, that narrows the number of commits we might need to consider when fixing the issue.
Thoughts? Concerns?
Contributor guide
Research direction
No files or tests are named. Start by reading the 42-comment discussion and reviewing how the Windows and Linux installers are produced around each build window. Done would mean a defined GitHub release process that ties both installers to the same commit and records known-working or broken snapshots.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100