Below are the steps used to prepare FSAdata for submission to CRAN. The steps should generally be followed in order (i.e., don't move to the next step without success at the current step). It is common to have to repeat some previous steps if an error/warning occurs at a subsequent step (in my experience, this most often happens after checking on the development version of R when using R-winbuilder).
It is worth noting that this whole process can take 2-3 hours (or more depending on internet speed) with significant "waiting time" for checks and builds.
0 - Preparatory Updates
[x] Update to latest R version.
[x] Update to latest RStudio version.
[x] Update all packages, especially those that FSA and FSAdata depend on.
[x] Ensure that all branches emanating from dev have been appropriately merged to dev via pull request.
[x] Update Version field in DESCRIPTION (next number up without the .9000 on the end).
[x] Update Date field in DESCRIPTION.
[x] Update Version in top header of NEWS.md (next number up without the .9000 on the end).
[x] Ensure that NEWS.md contains descriptions of all major changes (this is usually done in "real-time" as changes are being made).
[x] Create new cran-comments-vX_X_X.md file in cran-comments folder. This will likely just be a copy of the same file from the previous version, but may include notes specific to inquiries from CRAN operators. [Note that this will be used in Section 5 below, so leave the file open).
[x] Run pkgdown::build_site() in the console of RStudio.
2 - dev branch (at local repo)
[x] Run Build..Check in RStudio. Address all errors, warnings, and notes and redo parts of the previous section as necessary. [There should generally be no errors, warnings, or notes as the package should have been checked with each major change to dev. At times I will get a note about a new author or not being able to verify current time.]
[x] Build a "source package" in RStudio with More..Build Source Package.
[x] Upload source package to all three "flavors" at R-winbuilder. Wait for an e-mail reply from R-winbuilder. Any errors, warnings, or notes for any flavor should be addressed (after which this step, and possibly relevant steps above, should be repeated).
[x] Upload source package to both the "release" and "development" "flavors" at R-macbuilder. Monitor results (especially "Check Log") page (will be given a link upon submission). Any errors, warnings, or notes for any flavor should be addressed (after which this step, and possibly relevant steps above, should be repeated).
[x] Push changes from above from local machine to dev branch on GitHub.
3 - dev branch (at remote GitHub repo)
[x] Ensure that "R-CMD-check.yaml" GitHub action was successful for the dev branch (this should run automatically with the push to dev, but will take some time to finish (possibly >20 mins)). If not successful then address issues and repeat as much above as necessary.
[x] Create a pull-request asking to merge the dev branch to the main branch. Ask someone from the FSAdata team to review the request. [Ensure that all checks were successfully completed.]
4 - main branch (at remote GitHub repo)
[x] Merge approved (assumingly) pull request from dev branch.
5 - main branch (at local repo)
[x] Fetch the remote main branch and pull the updates to local main branch so that the local and remote main branches are the same.
[x] Build a "source package" in RStudio with More..Build Source Package.
[x] Build a "binary package" in RStudio with More..Build Binary Package.
[x] Goto the CRAN submission page. Enter your first and last names. Press Choose File and choose the source file (.tar.gz) created above. Copy the comments from the relevant cran-comments-vX_X_X.md and paste into the optional comments box. Press the Upload Package button.
[x] Review the ensuing page (it is usually correct) and press Submit Package button at the bottom.
[x] Wait for an e-mail from CRAN (this is usually pretty quick) and press the contained link to open a new webpage.
[x] Check all three boxes (make sure that your answers are truthful) and press Upload the Package to CRAN. You should get a confirmation e-mail almost immediately (no need to respond to this).
6 - main branch (at remote GitHub repo)
[x] Create a new release. Tag should relate to the version number and the Title should state that the version number is being released to CRAN (see past examples). Make sure that the Target is set to Main. Add an optional Description if desired. Drag and drop the source (.tar.gz) and binary (.zip) files created in the previous step on to the Attach binaries ... box. Press Publish Release.
7 - dev branch (at remote GitHub repo)
[x] Create a pull-request asking to merge the main branch to the dev branch. This is needed after merging dev to main above so that the two branches are synced.
[x] Merge pull request from main branch (OK to do this without getting approval from FSAdata team member). Note that the dev branch will say it is "1 commit ahead of main" after this step.
8 - dev branch (at local repo)
[x] Fetch the remote dev branch and pull the updates to local dev branch so that the local and remote dev branches are the same.
[x] Update Version field in DESCRIPTION by appending .9000 to the end.
[x] Create a new section at the top of NEWS.md with the new version number (i.e., including the .9000 on the end).
[x] Push these changes to the remote dev branch. This is the start of the next version.
droglenc
commented
1 year ago
Below are the steps used to prepare
FSAdatafor submission to CRAN. The steps should generally be followed in order (i.e., don't move to the next step without success at the current step). It is common to have to repeat some previous steps if an error/warning occurs at a subsequent step (in my experience, this most often happens after checking on the development version of R when using R-winbuilder).It is worth noting that this whole process can take 2-3 hours (or more depending on internet speed) with significant "waiting time" for checks and builds.
0 - Preparatory Updates
FSAandFSAdatadepend on.1 -
devbranch (at local repo)devhave been appropriately merged todevvia pull request.Versionfield in DESCRIPTION (next number up without the .9000 on the end).Datefield in DESCRIPTION.Versionin top header of NEWS.md (next number up without the .9000 on the end).cran-comments-vX_X_X.mdfile incran-commentsfolder. This will likely just be a copy of the same file from the previous version, but may include notes specific to inquiries from CRAN operators. [Note that this will be used in Section 5 below, so leave the file open).pkgdown::build_site()in the console of RStudio.2 -
devbranch (at local repo)dev. At times I will get a note about a new author or not being able to verify current time.]devbranch on GitHub.3 -
devbranch (at remote GitHub repo)devbranch (this should run automatically with the push todev, but will take some time to finish (possibly >20 mins)). If not successful then address issues and repeat as much above as necessary.devbranch to themainbranch. Ask someone from the FSAdata team to review the request. [Ensure that all checks were successfully completed.]4 -
mainbranch (at remote GitHub repo)devbranch.5 -
mainbranch (at local repo)mainbranch and pull the updates to localmainbranch so that the local and remotemainbranches are the same.Choose Fileand choose the source file (.tar.gz) created above. Copy the comments from the relevantcran-comments-vX_X_X.mdand paste into theoptional commentsbox. Press theUpload Packagebutton.Submit Packagebutton at the bottom.Upload the Package to CRAN. You should get a confirmation e-mail almost immediately (no need to respond to this).6 -
mainbranch (at remote GitHub repo)Tagshould relate to the version number and theTitleshould state that the version number is being released to CRAN (see past examples). Make sure that theTargetis set toMain. Add an optionalDescriptionif desired. Drag and drop the source (.tar.gz) and binary (.zip) files created in the previous step on to theAttach binaries ...box. PressPublish Release.7 -
devbranch (at remote GitHub repo)mainbranch to thedevbranch. This is needed after mergingdevtomainabove so that the two branches are synced.mainbranch (OK to do this without getting approval from FSAdata team member). Note that thedevbranch will say it is "1 commit ahead ofmain" after this step.8 -
devbranch (at local repo)devbranch and pull the updates to localdevbranch so that the local and remotedevbranches are the same.Versionfield in DESCRIPTION by appending .9000 to the end.devbranch. This is the start of the next version.