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

Decide how to name popler's package versions #28

Open
AldoCompagnoni opened this issue Mar 14, 2017 · 0 comments
Open

Decide how to name popler's package versions #28

AldoCompagnoni opened this issue Mar 14, 2017 · 0 comments

Comments

@AldoCompagnoni
Copy link
Contributor

Once we are ready for CRAN, we should know how to update package versions.
Example: 1.0.0.9000. The four elements of this sequence mean:

  1. Major change (New functions, maybe not be backwardly compatible)
  2. NewFeature (forgot what it means: find out)
  3. BugFixReleass (self-explanatory)
  4. development version (Hadley's recommendation)
@AldoCompagnoni AldoCompagnoni changed the title Decide how to name popler's package version Decide how to name popler's package versions Mar 14, 2017
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

1 participant