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

Upgrading from V2.0.2 to V3 #15

Closed
brianknott opened this issue Oct 16, 2018 · 1 comment
Closed

Upgrading from V2.0.2 to V3 #15

brianknott opened this issue Oct 16, 2018 · 1 comment

Comments

@brianknott
Copy link

Hi looking at upgrading to V3 but don't want to break the V2.0.2 processes.

Are there any upgrade issue of can I just replace the V2.0.2 process with V3

Brian

@lotsaram
Copy link
Collaborator

Hi @brianknott
When v3 of bedrock was done there was a lot of care taken around backwards compatibility. Any processes with the same name should have the same behaviour if run with the same parameters. For redundant or retired processes which are renamed or don't exist in v3 you can just leave these in the data directory in case they are referenced in custom processes. The best way to upgrade is simply to copy the v3 processes into a data directory containing the v2 processes and replace same named objects.
All behaviour should stay the same. But obviously you should test first in a non-production environment.

@lotsaram lotsaram closed this as completed Dec 6, 2018
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

No branches or pull requests

2 participants