Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.3.0 release (package release) #36

Open
matsmahnken opened this issue May 4, 2020 · 9 comments
Open

0.3.0 release (package release) #36

matsmahnken opened this issue May 4, 2020 · 9 comments
Milestone

Comments

@matsmahnken
Copy link
Contributor

I have closed all pending issues and included changes in branch 0.3.0 to prepare the release of ProfoundData v. 0.3.0 to CRAN.

What else do we need to do?

  1. Look at Travis CI build errors that come up in some commits (1fdd02f & c5a6107) and in the pending pull request include updates for the new DB version #35
    Don't know what exactly this tool does - need some help here.
  2. wait 1-2 days for the registration of the new DOI for DB version 0.3 because only then the new DOI links in the vignettes will work.
@florianhartig florianhartig added this to the Release 0.3.0 milestone May 4, 2020
@florianhartig
Copy link
Member

OK, I'm working on this - is there anything to update in the vignette?

@florianhartig
Copy link
Member

Is the paper already published / has a final DOI? In this case, that should definitely be updated!

@florianhartig
Copy link
Member

OK, the branch builds now, it was a problem with a dependency in the travis yml

@matsmahnken
Copy link
Contributor Author

That sounds good! The paper is not published yet - but we are handing it in latest on Wednesday (06.05.): https://www.earth-syst-sci-data-discuss.net/essd-2019-220/

@matsmahnken
Copy link
Contributor Author

The DB v. 0.3 is now released with a new DOI: http://doi.org/10.5880/PIK.2020.006
Links in the vignettes of branch 0.3.0 pointing to this DOI should be working from now on.

@matsmahnken
Copy link
Contributor Author

I think we have everything except for the final DOI of the data paper - should we continue the push of release/version 0.3.0 to CRAN?

@matsmahnken
Copy link
Contributor Author

The new DOI is published and the data paper is accepted for final publication. Now we can continue pushing version 0.3.0 to CRAN.
@florianhartig what else do we need to do before pushing the new version to CRAN?

@florianhartig
Copy link
Member

ae, basically we have to ensure that everything tests out

@florianhartig
Copy link
Member

I will create a pull request for the 0.3.0 branch and request a review from you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants