Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/501
Closed in favor of #595
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and w
Github user pluradj commented on the issue:
https://github.com/apache/tinkerpop/pull/501
Created https://issues.apache.org/jira/browse/TINKERPOP-1608
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does no
Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/501
Anyone who has an account can create issues. In fact, I just checked and I
think you should even have right such that you can assign them to yourself (i
see your account there as "joshsh"). Can
Github user joshsh commented on the issue:
https://github.com/apache/tinkerpop/pull/501
Thanks for the info, @spmallette. I will also look harder at graph
migration as in IoGraphTest. Note that I do not appear to have the
create-issue permission in JIRA.
---
If your project is set
Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/501
@joshsh - thanks - note that we still support 3.1.x (mostly for
maintenance) on the tp31 branch, 3.2.x on the tp32 branch (for maintenance and
non-breaking new features) and then do all dev for
Github user okram commented on the issue:
https://github.com/apache/tinkerpop/pull/501
Can you please make corresponding JIRA tickets and use the PR naming
convention for your PRs? Also, this PR will need documentation as well as an
update to the CHANGELOG. Finally, I don't know why t
