rstan releases are tagged but not "released"
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 1.1k
- Forks
- 266
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 1
Description
There are tags for rstan releases (e.g. there's a v2.19.2 tag) but on GitHub the last release is listed as v2.8.0 from 2015. GitHub is changing their webpage layout for repos and now it says prominently "Latest release v2.8.0 on September 28, 2015" (see red circled area in screenshot below).
For future rstan releases a release should be both tagged and actually "released". This is good practice in general but especially when GitHub now advertises the latest release date on the main repository page:
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 reviewing the repository's current release process and the existing rstan tags and GitHub releases, focusing on how a tagged release becomes visible as a GitHub release. Done means future rstan release tags are accompanied by corresponding GitHub releases and the repository no longer advertises the outdated release as latest.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, r
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100