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

[ACC-335] upgrade blueprints neo4j to 2.3.1 #540

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mffrench
Copy link

Dear blueprints 2.x maintainers,

I upgraded blueprints neo4j2 to use the last neo4j distribution 2.3.1.
Let me know if you see anything wrong blocking this pull request for merge ...

Thank you

@spmallette
Copy link
Member

Are you aware that development on TinkerPop 2.x has stopped? All work is on TinkerPop 3.x at this point: http://tinkerpop.apache.org In 3.x we support later versions of Neo4j.

I don't think there's a problem with us merging in your PR, but we don't expect to have any new releases of any of the TinkerPop 2.x projects so.......

@mffrench
Copy link
Author

Yeah I'm aware 2.X is in maintenance mode which also means for me : be able to upgrade the neo4j DB version (if there is not so much changes).

Regarding TinkerPop 3, we first need to migrate from java 1.7 to java 1.8 as far as I understood so we will migrate to tinkerpop 3 after our java migration. Meanwhile we would like to upgrade our Neo4j database.

If you don't plan any new release on tinkerpop 2.x for maintenance tasks (ie : some upgrade or corrections), you should not say tinkerpop 2.x is in maintenance mode but is definitively closed... In such case we will manage our own release...

Thank you

@spmallette
Copy link
Member

If you don't plan any new release on tinkerpop 2.x for maintenance tasks (ie : some upgrade or corrections), you should not say tinkerpop 2.x is in maintenance mode but is definitively closed

hmm - that's a good point actually. maybe that's bad terminology at this point (meaning we've been in "maintenance mode" for a while but maybe we're not anymore). i'll bring that up on the dev list.

@mffrench
Copy link
Author

OK ! I'm currently working on a special release to use neo4j 2.3.1 with blueprint 2.x on a dedicated branch... I guess this will be the last (unofficial) blueprint 2.x release but let me know if you plan a last official release on 2.x (maybe there is some correction you would like to provide with 2.7 ?).

Cheers,

Mathilde

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

Successfully merging this pull request may close these issues.

2 participants