Open JamesHWade opened 5 months ago
@calderonsamuel, I'm coming back from parental leave soon, and I want to give a lot more time to this package. Thought I'd start that off with an "upkeep" issue created with usethis::use_upkeep_issue()
.
Anything else you'd like to add? After this, it seems like a good time to issue a new release given all your fantastic recent contributions.
Hi James, glad to have you back! I think we need to solve the bugs listed in issues and improve some documentation.
I would also like to have some features implemented before v0.4.0:
Thinking a bit about the near future, I think we should aim to achieve two things:
At some point we should reach an actual stable version. I would like to have these features, they are both pretty challeging:
Great ideas. I updated them to tasks for us to work on. Thanks again for all of you fantastic work on this package! I'm excited by your {skellm}
package.
@calderonsamuel, you might be interested in this PR from httr2:
https://github.com/r-lib/httr2/pull/437
It might make our lives a lot easier in parsing JSON from streams.
@calderonsamuel , I'd like to submit 0.4 to CRAN with in the next few weeks. Do you think you'll have time to work on some of the items you mention above over the newt couple of weeks?
If so, let me know what you plan to work on, and I'll try to cover any of the remaining tasks.
@calderonsamuel , I'd like to submit 0.4 to CRAN with in the next few weeks. Do you think you'll have time to work on some of the items you mention above over the newt couple of weeks?
If so, let me know what you plan to work on, and I'll try to cover any of the remaining tasks.
Hi James. I can focus on reducing the hard coded css and the dynamic model selection. Also I can help with fixing bug reports
Hey James, I think we should push v0.4.0 to CRAN and move the pending issues to v0.5.0. The current CRAN version crashes in different scenarios that have long been fixed in the develpment branch. Also, lots of newbies don't know how to install from github. Just give time to fix #202 and we should be good to go
Let's do it. Is next week a good target?
I'll plan to send this off to CRAN tomorrow unless I hear any objections. Excited to get this next version out there!!!
I'll just like your opinion on keeping the following elemets:
They were useful for the development, but I'm not sure if final users will them useful too.
I use them all the time, so I say keep them.
I have a lot of small updates in my mind, but I don't want us to lose the momentum. Lets go to CRAN
I have it ready to submit Monday morning. I forgot they don't like submissions on the weekends.
usethis::use_tidy_description()
R/
files andtest/
files for workflow happiness. The docs forusethis::use_r()
include a helpful script.usethis::rename_files()
may be be useful.Set up or update GitHub Actions. \ Updating workflows to the latest version will often fix troublesome actions:
usethis::use_github_action('check-standard')
usethis::use_github_action('pkgdown')
usethis::use_github_action('test-coverage')
Created on 2024-01-08 with
usethis::use_upkeep_issue()
, using usethis v2.2.2