Issues with the experimental version of 2.26 from PR #887
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 1.1k
- Forks
- 266
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 1
Description
https://github.com/stan-dev/rstan/pull/887 is huge and I think the PR thread will eventually become impossible to follow. So I am opening this issue where you can post anything that is missing in the alpha 2.26 version.
Thanks @hsbadr for working on this massive pull request!
I think the checklist for making this happen is as follows:
-
Check that it works for the early-adopters/devs on all OS-es for R4.x (R-release)
-
Check that it works for the early-adopters/devs on all OS-es for R3.x (R-oldrel)
I think after this we can merge the PR and deal with smaller issues later.
-
Make a beta-call on Discourse for other users with a disclaimer that it might break other packages that depend on rstan.
-
Hash out issues after the beta call
-
Try to get this to CRAN - this is where my knowledge stops. I expect this is where the "fun" will start.
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 PR #887 and its thread, then use this issue's checklist as the coordination plan. Verify the alpha on all OSes with R-release and R-oldrel, organize the proposed Discourse beta call, track resulting issues, and determine the CRAN submission steps. Done means the compatibility checks and beta feedback are addressed and the release is ready for CRAN.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100