CRAN submission

[strengejacke]

@IndrajeetPatil What do you think about submitting a new release to CRAN the next days? I'm planning to submit parameters, but that would break see (nothing to do here, the dev-version of see has already fixed this issue). So we would need to submit both packages within a certain time frame.

[IndrajeetPatil]

Sure, just let the CRAN team know that you’ve informed the maintainer and the update is on the way for broken package. I can then update *see* once *parameters* update is on CRAN.

…

On Fri 2. Feb 2024 at 21:13, Daniel ***@***.***> wrote: @IndrajeetPatil <https://github.com/IndrajeetPatil> What do you think about submitting a new release to CRAN the next days? I'm planning to submit *parameters*, but that would break *see* (nothing to do here, the dev-version of *see* has already fixed this issue). So we would need to submit both packages within a week or so. — Reply to this email directly, view it on GitHub <#320>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACWOHFNIEWCZZF45OLNAQLTYRVCGDAVCNFSM6AAAAABCXHSNJOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYTKNZRGQYDCNI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[strengejacke]

Ok parameters is on CRAN

[strengejacke]

We could merge #321 before submission.

[strengejacke]

ok, I think you can submit. I also need to submit a hotfix of parameters due to breaking changes in marginaleffects. Should we submit see first, then parameters hotfix, or other way around?

[IndrajeetPatil]

You can submit the hotfix first, and then I can check see against this version and submit.

[strengejacke]

parameters on CRAN!