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.

Sign up for GitHub

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

Jump to bottom

No releases are tagged #290

Open
QuLogic opened this issue Nov 5, 2017 · 1 comment
Open

No releases are tagged #290

QuLogic opened this issue Nov 5, 2017 · 1 comment

Comments

@QuLogic
Copy link

QuLogic commented Nov 5, 2017

Several releases have been made to CRAN, but none of them have been tagged here. This makes it difficult to find the exact commit from which any release originated.
@timelyportfolio
Copy link
Collaborator

@ramnathv, @jcheng5 I agree that for stability and robustness, we should tag future releases on Github starting with current. I am not sure there is much benefit in back-tagging releases. Please let me know how I can help. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@QuLogic @timelyportfolio