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

Odoo v10 for Turnkey (v14.2) #78

Open
DocCyblade opened this issue Jun 22, 2017 · 10 comments
Open

Odoo v10 for Turnkey (v14.2) #78

DocCyblade opened this issue Jun 22, 2017 · 10 comments

Comments

@DocCyblade
Copy link
Owner

@l-arnold I am starting down the road to Odoo v10 (skipping 9) for TKL v14.2

@l-arnold
Copy link
Collaborator

Would be a pretty good time for me to jump back in. Memory banks a bit out of tune is all.

Lets discuss.
Landis

@l-arnold
Copy link
Collaborator

Lets try to also keep a version 8.0 intact. Some people may want the tkl upgrade without the odoo one.

I want to see if we can have OpenUpgrade. Work to migrate from 8 to 10.

@JedMeister
Copy link

Hey guys. Whilst it might be nice to produce a "final" v8 Odoo appliance, it will reach EOL in a few months (when v11 is released) so would be of pretty limited value IMO. The only real value would be to existing TurnKey users who wanted to migrate to it via TKLBAM. But that wouldn't really provide much advantage as the backup will include the version of Odoo which the appliance shipped with...

So I would argue that going straight to Odoo10 is better use of time/resources.

Having said that, documenting a migration pathway from the existing appliance (with v8) to a new appliance (with v10) would be a really good idea IMO.

@BillDStrong
Copy link

Actually a last odoo 8 version, as many modules that are needed for specialty applications are still not available for odoo 10. (Some are just being updated for version 9, which you plan to skip). While I agree that 8.0 is EOL creates a barrier, I would like to point out that the OCB project is some 300 commits ahead of the main odoo branch, and might be a better target to maintain for its usefulness. Even if it is only for one last release.

@l-arnold
Copy link
Collaborator

@BillDStrong 's comment is important.
I feel it is important to keep support for Odoo (Branch) 8.0. From my view, also integrating support for Odoo (Branch) 10.0 would make sense as the next stage.

Moving to 11.0 is a non-starter. VERY MUCH of the Ecosystem for Odoo (OCA Particularly) has not been migrated to support 11.0 effectively. Version 10, Odoo is pretty good. Version 8.0 is the most important fall back, in my view.

Do we have a "migration" method in place jumping to Version 11.0? Normally such a migration needs to go through a step by step upgrade and I am sure cannot jump 3 versions. Perhaps there are some TKL tricks that will facilitate this but seems complicated.

@JedMeister
Copy link

@l-arnold - Odoo v8 is now EOL and unsupported. Really we should pull the current appliance! We're not going to be releasing another build with software that is unsupported by upstream.

There is no migration method that I am aware of. And I don't see anyway that TurnKey will be able to do anything to assist that. I think it will be a case of manually migrating to the newer version on your current server, then once you're up to a version matching the current TurnKey release (once there is one) then manually migrating the data across (to take advantage of the new OS etc). TKLBAM can be used to bundle up everything, but I would not recommend just doing a normal "restore". I think the best plan would be to do a data dump, then manually move everything to the required locations.

TBH, I imagine that it will be a massive PITA! If you'd like to start working on it and document as you go, then that'd be super awesome and I'm sure others would appreciate it!

Whilst the Odoo software itself seems pretty awesome, the way they maintain it and manage updates seems pretty painful for me. I don't see anyway that TurnKey can really make that any better.

All we can do is make the initial install easier. After that, I think it's going to be a bit of "every man for himself". If the (TurnKey) community can get behind it and help each other out, we're happy to do what we can to support that, but we don't have the resources to do much more than we already do. We have another 99 odd appliances to maintain and our resources are already pretty stretched - v15.0 is already 6 months overdue!

@JedMeister
Copy link

Oops, a quick google showed that there is indeed something of a migration script:

https://doc.therp.nl/openupgrade/

I also found a blog post which is quite dated (and only covers up to v10) but the workflow looks pretty good, so should still be of some value:

https://xpansa.com/odoo/how-to-do-odoo-upgrade/

Also the OCA GitHub repo has a wiki page which also might be of some value:

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-11.0

(PS apologies too if I come across as being a bit crabby; I'm just a bit stressed out that the v15.0 release is so far behind schedule. The thought of more extra work makes me feel a bit despondent really...)

@l-arnold
Copy link
Collaborator

l-arnold commented May 14, 2018 via email

@l-arnold
Copy link
Collaborator

l-arnold commented May 14, 2018 via email

@l-arnold
Copy link
Collaborator

l-arnold commented May 14, 2018 via email

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

4 participants