Downstream Deprecated / Expired Syntax
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 1.1k
- Forks
- 266
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 1
Description
Opening this issue to track the status of downstream packages. All dependencies have now had PRs submitted or the maintainers notified.
Status
- Patches not yet merged: 23
- Patches merged, not yet on CRAN: 15
Patches not yet merged
| Package | Status | Merged | On CRAN |
|---|---|---|---|
| AovBay | Maintainer emailed | ||
| bbmix | PR Opened | ||
| BINtools | Maintainer emailed | ||
| bmggum | PR Opened | ||
| bws | PR Opened | ||
| cbq | PR Opened | ||
| densEstBayes | Orphaned | ||
| fcirt | PR Opened | ||
| glmmPen | PR Opened | ||
| hBayesDM | PR Opened | ||
| idem | PR Opened | ||
| imt | PR Opened | ||
| MetaStan | PR Opened | ||
| multipleDL | PR Opened | ||
| oncomsm | PR Opened | ||
| morseTKTD | |||
| phacking | PR Opened | ||
| psBayesborrow | PR Opened | ||
| rts2 | PR Opened | ||
| spsurv | Github Stan code broken issue opened | ||
| survstan | PR Opened | ||
| truncnormbayes | PR Opened | ||
| YPPE | PR Opened |
Patches merged, not yet on CRAN
| Package | Status | Merged | On CRAN |
|---|---|---|---|
| bayesforecast | PR Opened | ☑️ | |
| beanz | PR Opened | ☑️ | |
| bmstdr | PR Opened | ☑️ | |
| bsynth | PR Opened | ☑️ | |
| CARME | PR Opened | ☑️ | |
| cloneRate | PR Opened | ☑️ | |
| CNVRG | PR Opened | ☑️ | |
| DCPO | PR Opened | ☑️ | |
| jfa | PR Opened | ☑️ | |
| mlts | PR Opened | ☑️ | |
| publipha | PR Opened | ☑️ | |
| rcbayes | PR Opened | ☑️ | |
| trialr | PR Opened | ☑️ | |
| WhiteLabRt | PR Opened | ☑️ | |
| zoid | PR Opened | ☑️ |
EDIT: Will now remove rows once packages updated on CRAN
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 downstream package status tables and the linked pull requests and issue to determine which compatibility patches remain unresolved. Done means the affected packages are updated on CRAN and their rows can be removed as described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- release
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100