releaseNotes #130
Comments
|
technically it can be either a URL or a URN (i.e. a namespace followed by an identifier, like |
|
For R packages could there be URN? |
|
and should I try and do the updates proposed above on Monday? |
|
timing wise is up to you. Not sure what a URN would be for an R package, it would be technically valid to do |
|
I mean before or after the CRAN release, which is up to you 😉 |
|
hah, I thought I just did what you told me to do! Pointing to GitHub release page as first choice seems reasonable. May as well wait for this, doesn't sound like we're in a rush to get the release since |
|
Cool then I can pack all my badges madness into 0.1.6 😀 and add releaseNotes URL 😀 |
|
I'll add code to point to "general" releases page (GitHub one, and NEWS file on CRAN/BioConductor if GitHub releases page doesn't exist). Now I guess the actual releae note related to a release, along with an ID etc. are something to be discussed in #135 |
|
I think it'd actually make little sense to have the general releases/NEWS page in this field since it's supposed to be the release notes of that given version. |
* add pre-commit hook for DESCRIPTION vs codemeta.json * oops had forgotten the dependencies 😱 * had also forgotten to import the function * puts the code in the right place and documents what the first call to write_codemeta will do * add rOpenSci and myself as authors * remove MIT licence * change licence * add that the code is GPL-3 * replaces devtools with usethis where possible * mostly French snobism 😉 * add uses_git origin * cf ropensci#62 * ropensci#62 * only adds hook once! * start using desc cf ropensci#41 * various fixes * better example? * document * removes reference to deleted function * cf ropensci#63 * cf ropensci#64, parses more possible roles * updates codemeta.json in particular more people/orgs appear * start work on opinions cf ropensci#76 * document * oops * oops again * gives opinion when verbose=TRUE and otherwise just uses robust code * cleans up tests * more tests of plain authors&maintainer * work on tests * corrects documentation * better if the pkg exists 😁 * update codemeta * adds a message to get a devtools release question * fix? * new try * removes httr dependency in favor of crul cf ropensci#83 * checks URLs in DESCRIPTION cf ropensci#68 * oops fixes test * uses dev version of jsonld * adds coercion to character to repair bug introduced by jsonld new version cf ropensci#88 * clean up cache * yay encoding * close ropensci#84 by deleting now useless licences.R file * appveyor * oh, Appveyor * start filling NEWS.md * better checks when several URLs * more space * generate review metadata cf ropensci#23 * oops * cf ropensci#63 * @jeroen said that this might help 🙏 * thanks again @jeroen * test on patched R version * CRAN and Bioconductor links for dependencies cf ropensci#81 * add tests of dependencies URL creation * add canonic URL for the package itself cf ropensci#81 * borrows jsonlite code cf ropensci#84 * makes it a bit more specific * badge parsing cf ropensci#130 * uses badge parsing function in guess_metadata * opinions about README cf 98 * add check of provider cf ropensci#81 * oops * oops again * R CMD Check NOTEs * oops * update contributor list cf ropensci#95 * several relatedLinks cf ropensci#99 * add the URL only once * oops repairs test * update NEWS * add ability to provide relatedLink for packages installed from CRAN or Bioconductor * add link to commit if available * only one maintainer currently cf ropensci#109 * oops this was wrong! * mmmh there was a mistake here * Travis fix? * remotes cf ropensci#96 * Travis fix? * export the badge extraction function cf ropensci#107 and update docs and correct a test * status as URL cf ropensci#102 * now one can extract lifecycle status * not only Travis CI as contIntegration cf ropensci#111 * update NEWs * update NEWS * repairs handling of additional terms cf ropensci#112 and adds corresponding test * correct test
A few questions
It has to be something online right?
when there is a GitHub repo
Should it actually point to something like https://github.com/ropensci/ropenaq/releases ?
Or the latest release thanks to https://developer.github.com/v3/repos/releases/#get-the-latest-release ?
When there is no GitHub repo should it try and find the release notes at the provider e.g. https://cran.r-project.org/web/packages/HIBPwned/news.html or https://bioconductor.org/packages/release/bioc/news/a4/NEWS ?
The text was updated successfully, but these errors were encountered: