Open tyner opened 1 month ago
Hi @tyner, Sorry about that. However every time I regenerate paws. Hundreds of method get updates/changes across the entire sdk. For example:
paws 0.7.0: https://github.com/paws-r/paws/pull/826
There are around 752 files changed. Due to this, it is very difficult to document all the changes. However I am open to ways for this to be captured 😄 Ideally it would be good to automate this to reduce the overhead for each paws release.
Due to the size of these updates I am finding it difficult to document them. Instead of tracking paws sdk changes we have opted to keep track of paws.common
. As it underpins all of paws. Any improvement in paws can be found within paws.common i.e. bug fixing, performance enhancements etc....
I am still open to tracking each version change of paws, however I want to do it in an automated way to reduce the overhead of the release process.
Thanks for clarifying. In the meantime perhaps the paws NEWS file could say something to the effect of "for a more comprehensive list, please see the paws.common NEWS" ?
Not a bad idea :) I will add that shortly.
The versioning in the
NEWS
file shows entries from version 0.1.0 through version 0.1.12; the latter being released to CRAN back on 9/3/2021. Somehow versions 0.2.0 through 0.7.0 do not have entries in theNEWS
file. Is this an oversight?