Thanks to all for the responses and suggestions.
I was primarily proposing a more detailed change log for packages on CRAN. To
my mind, repositories like R-forge host packages more 'raw' than those on CRAN
(i.e. CRAN seems to me to contain more 'finished' packages which occasionally
are updated
One "other similar location" is Github, where you can "watch" a
package, and this is how I keep track of changes in the packages that
I'm interested in.
Just for the interest of other R package developers, the NEWS file can
be written in Markdown and I have a Makefile
(https://github.com/yihui/kni
On 10/2/2012 10:01 AM, Starkweather, Jonathan wrote:
I'm relatively new to R and would first like to sincerely thank all
those who contribute to its development. Thank you.
I would humbly like to propose a rule which creates a standard (i.e.,
strongly encouraged, mandatory, etc.) for authors to
There is already support in the packaging system for a NEWS file which
can be accessed within R using the 'news' function. What would the
changelog that you are proposing contribute or contain beyond what the
NEWS file already does?
Creating and updating NEWS is not mandatory, but is encouraged.
I'm relatively new to R and would first like to sincerely thank all those who
contribute to its development. Thank you.
I would humbly like to propose a rule which creates a standard (i.e., strongly
encouraged, mandatory, etc.) for authors to include a `change log' documenting
specific changes
5 matches
Mail list logo
