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

Tag a new version #32

Closed
dpsanders opened this issue Aug 17, 2015 · 3 comments
Closed

Tag a new version #32

dpsanders opened this issue Aug 17, 2015 · 3 comments

Comments

@dpsanders
Copy link
Contributor

I think we should tag at least a new patch version.
@lbenet
Copy link
Member

lbenet commented Aug 17, 2015

I've been thinking about this as well. Shall we include in the tagged version an improvement related to #24, and perhaps #30 as well?

@lbenet
Copy link
Member

lbenet commented Aug 22, 2015

I will update the documents with the new improvements before tagging a new version

@lbenet lbenet mentioned this issue Aug 25, 2015
Merged
@lbenet
Copy link
Member

lbenet commented Aug 27, 2015

New version is tagged. In the documentation I only updated the bechmarks vs Mathematica (after tagging). I close this

@lbenet lbenet closed this as completed Aug 27, 2015
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
@dpsanders @lbenet