Skip to content

Identify changes from Dev for Master #11

@jknowles

Description

@jknowles

I'd like to see all of the current functionality in the dev branch move to master. Then make the master branch be fixed and stable and work on building unit tests and package infrastructure and submitting a robust build to CRAN. Meanwhile the dev branch becomes a place to look at adding package extensions like Excel support and HTML support for work with rmarkdown.

I think the easiest way to do this might be to merge, and then to start divying up infrastructure tasks. I'm happy to start building the unit tests for the pieces of functionality I have submitted and to keep track of any errors.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions