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

Gem should test against Neo4j 2.2.2, not 2.2.1 #847

Closed
subvertallchris opened this issue Jun 23, 2015 · 3 comments
Closed

Gem should test against Neo4j 2.2.2, not 2.2.1 #847

subvertallchris opened this issue Jun 23, 2015 · 3 comments

Comments

@subvertallchris
Copy link
Contributor

No description provided.

@cheerfulstoic
Copy link
Contributor

Should test against comunity-latest

Also we should probably test the latest versions of 2.1.x and 2.2.x (and maybe 2.3.x / 3.0.x?). We might do that via the mechanism described here:

neo4jrb/neo4j-rake_tasks#1

@subvertallchris
Copy link
Contributor Author

I think we were using this at one point, weren't we? I feel like I had to
roll it back but I can't remember why beyond "broken."

On Thursday, September 10, 2015, Brian Underwood [email protected]
wrote:

Should test against comunity-latest

Also we should probably test the latest versions of 2.1.x and 2.2.x (and
maybe 2.3.x / 3.0.x?). We might do that via the mechanism described here:

neo4jrb/neo4j-rake_tasks#1
neo4jrb/neo4j-rake_tasks#1


Reply to this email directly or view it on GitHub
#847 (comment).

@cheerfulstoic
Copy link
Contributor

Yup, I don't recall why either. Just trying to give context in case somebody else picks it up ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants