Setup nightly releases
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 355
- Forks
- 24
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 17
Description
To get quick turnaround and feedback on what we implement, I believe it would be extremely beneficial if we implemented nightly beta releases. Since the LSP auto-updates its own dependencies, we could make it so that users with experimental features enabled get beta versions of the indexer.
That will allow us to get quick feedback if we make mistakes and we can compare the performance of the analysis between the beta versions before cutting a stable release.
AFAIK, as long as the version is bumped to something like 0.1.0.beta1, Bundler will not accept that in regular updates, so we have complete control over when the nightly builds get installed.
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. Start by mapping the repository's current versioning and release workflow, then determine how beta versions would reach users with experimental features without entering regular Bundler updates; done means nightly beta builds are produced and stable users remain unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby, rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100