Release new version #140
Comments
|
|
Re: PDF export, can we just download the badge image and include it in a link? But in any case, adding the DOI link (dx.doi.org/...) makes sense. |
|
LGTM Maëlle! Nothing further to add to this release. |
|
blog post/tech note draft ropensci-archive/roweb2#452 I'm aiming for a release next week. @geanders @lmullen @melvidoni any comment on this issue? |
|
👍 Looks good! |
|
@geanders @melvidoni any comment on/wish for the upcoming release (see thread above)? |
|
Looks good! |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the beginning of May, since we planned to have a release every 3 months.
For diff see #139. See preview at https://devdevguide.netlify.com/ NEWS below
2019-04-23, add link to Daniel Nüst's notes about migration from XML to xml2.
2019-04-22, ask reviewer for consent to be added to DESCRIPTION in review template.
2019-04-22, use a darker blue for links (feedback by
@kwstat, light blue text in the book is awfully hard to read #138).2019-04-22, add book cover.
2019-04-08, improve formatting and link text in README (
@katrinleinweber, A few minor ReadMe improvements (formatting & link texts) #137)2019-03-25, add favicon (
@wlandau, Attempt to add a favicon #136).2019-03-21, improve Travis CI guidance, including link to examples. (
@mpadge, update pkg_ci; closes #133 #135)2019-02-07, simplify code examples in Package Evolution section (maintenance_evolution.Rmd file) (
@hadley, Code tweaks to evolution #129).2019-02-07, added a PDF file to export (request by
@IndrajeetPatil, making a pdf copy available for the book #131).There'd be an accompanying tech note cc @stefaniebutland.
@ropensci/editors is there any other currently open issue you'd like to see tackled (whether you can help or not) before the next release?
@noamross I am not sure how to make the DOI appear well in the PDF book (the badge won't work), what would be the best solution? A link to Zenodo after the sentence mentioning the license?
The text was updated successfully, but these errors were encountered: