Can't build package due to some missing commas. about eml HOT 6 CLOSED

Thanks. Yeah I should refrain from pushing things that can't install.... Given that we're teaching with this I should probably start a development branch rather than breaking master all the time!

from eml.

Not to worry. Not going to update the package on the AMI for the coming week.

On Wed, Sep 4, 2013 at 10:45 AM, Carl Boettiger [email protected]
wrote:

Thanks. Yeah I should refrain from pushing things that can't install.... Given that we're teaching with this I should probably start a development branch rather than breaking master all the time!

Reply to this email directly or view it on GitHub:
https://github.com/ropensci/reml/issues/44#issuecomment-23809266

from eml.

I'm also looking into it since my life is now a flood of meetings about metadata here at neon and there's some small consensus that we might go with eml and I'm pointing people towards the package. Nice to have a working branch that I can show off here.

from eml.

Okay, I now have a devel branch (also pushed to this github repo) that I'll mess around with, and I'll keep master stable (Installing and passing the test suite at least). Will try and flush out documentation on master.

The current master branch (1ee0bc3) now passes all tests and installs (needs more documentation etc to pass Check....). I'm developing on devel. At this point reml does most of the basic necessities: just closed the next milestone now that we can add coverage metadata. We can read in, write out, and publish basic EML files.

Note that the top-level API might still need to change a bit as we support more optional fields and need ways the user can modify them...

Great to hear about interest in the package (at least among us!). Will push towards a stable version on CRAN in the near future (that is, freezing the user-facing functions API). File issues and bugs and requests!

from eml.

@cboettig What is the API here? Are you referring to the internal plumbing?

from eml.

@karthikram Correct, I use the term API to refer to any function exported by the NAMESPACE. It's the "API" because exported functions are designed to be available to other packages (as well as the end-user, obviously), and hence are the interface for both users and applications and should be stable once released (or otherwise justify at least a change to the major number in the semantic versioning).

from eml.