DocCyblade / tkl-odoo

Turnkey Linux - Odoo v8 (Published v14.2)
https://www.turnkeylinux.org/odoo
GNU General Public License v3.0
21 stars 24 forks source link

Odoo v10 for Turnkey (v14.2) #78

Open DocCyblade opened 7 years ago

DocCyblade commented 7 years ago

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

l-arnold commented 7 years ago

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 commented 7 years ago

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 commented 7 years ago

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 commented 7 years ago

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 commented 6 years ago

@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 commented 6 years ago

@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 commented 6 years ago

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 commented 6 years ago

Hi Jeremy, I know its a pain. I am turning my tkldev server back on. It will take a lot of old notes to get back to speed.

FYI though, EOL is not EOL in Odoo World. Many many people, businesses and developers are using Odoo 8 (9 and 10). OCB is a full Branch take on Odoo. It is only the "company" Odoo which is not supporting Odoo 8. ODoo are basically trying to force feed support.

Even still, https://github.com/odoo/odoo/branches/all Active work is being done on V 9 and V10 on Odoo, and Git is there going back to V6 on Odoo and V5 on OCA (Odoo Community Association). OCA is supporting Branches back to V 5 and

This is a good "reference" for what is really being supported and my view is that 11 is not really ported by the community yet. https://github.com/oca/

V 10 is quite supported by usable community module ports, and even still you will see here docs are still pointing at v8.0 OCA has ported most of the Connector series to 10 now. http://odoo-magento-connector.com/project/contribute.html.

OpenUpgrade is here: (See the Branch Structure). I have not yet used it but you can't use it till all your modules are ported and generally modules are "alive" at 10.0.... https://github.com/OCA/OpenUpgrade Their Branch structure goes back to V5 even.

I will do some testing. Just really hoping we can aim for 10 not 11.

Sorry for the trouble caused just in bringing up the subject (I do think I have been consistent on this subject).

Thank you for all your hard work! I know of the volume and the breadth of it.

Landis

From: "Jeremy Davis" notifications@github.com To: "DocCyblade/tkl-odoo" tkl-odoo@noreply.github.com Cc: "Landis Arnold" larnold@nomadic.net, "Mention" mention@noreply.github.com Sent: Sunday, May 13, 2018 6:30:27 PM Subject: Re: [DocCyblade/tkl-odoo] Odoo v10 for Turnkey (v14.2) (#78)

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

[ https://doc.therp.nl/openupgrade/ | 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/ | 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 | 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...)

— You are receiving this because you were mentioned. Reply to this email directly, [ https://github.com/DocCyblade/tkl-odoo/issues/78#issuecomment-388667655 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AFaR6AwjzoWqMgZwAp1ISRtIZ_DfcSUKks5tyNAjgaJpZM4OBwU3 | mute the thread ] .

l-arnold commented 6 years ago

Jeremy and TKL Team, Sorry to even post this re Odoo but... In Github: https://github.com/odoo/odoo/branches/all?page=1

8.0 is still "Open" on Git even for updates. 7.0 and 6.1 are closed. 6.0, inextricably is "Open".

OpenUpgrade is "Active" on Branch 8, 9 and 10. Default is 11 but I don't know if it is "working" yet. Likely so but..

More important even to me: In terms of the Magento Connector which I rely upon very much (and the reason I wanted the Odoo Appliance in the first place) if you look at the Folder Structure of Branch 10 vs Branch 11 you will see very few folders in V 11. I really do not believe it is running in 11X I know it is running in version 10:

https://github.com/OCA/connector-magento/tree/10.0 https://github.com/OCA/connector-magento/tree/11.0 (the readme says it is running but there are nearly no folders in the Git for Branch 11)

There are several other important subjects, POS (Point of Sale) that are also critical for running a business. The same Equation holds. Look at the Folder Structure of branch 10 vs branch 11. 10 is built (see the sub modules in their folders -- ie credit card readers). https://github.com/OCA/pos/tree/10.0

nearly nothing in 11 https://github.com/OCA/pos/tree/11.0

We need to be able to process our orders, make our goods, and accept credit cards. That is doable now in Version 8 and Version 10 of Odoo. 11 is a stretch IMHO.

All for now. thank you for reading and all your hard work.

Landis

From: "Landis Arnold" larnold@nomadic.net To: "DocCyblade" reply@reply.github.com Cc: "DocCyblade" tkl-odoo@noreply.github.com, "Mention" mention@noreply.github.com Sent: Sunday, May 13, 2018 7:01:42 PM Subject: Re: [DocCyblade/tkl-odoo] Odoo v10 for Turnkey (v14.2) (#78)

Hi Jeremy, I know its a pain. I am turning my tkldev server back on. It will take a lot of old notes to get back to speed.

FYI though, EOL is not EOL in Odoo World. Many many people, businesses and developers are using Odoo 8 (9 and 10). OCB is a full Branch take on Odoo. It is only the "company" Odoo which is not supporting Odoo 8. ODoo are basically trying to force feed support.

Even still, https://github.com/odoo/odoo/branches/all Active work is being done on V 9 and V10 on Odoo, and Git is there going back to V6 on Odoo and V5 on OCA (Odoo Community Association). OCA is supporting Branches back to V 5 and

This is a good "reference" for what is really being supported and my view is that 11 is not really ported by the community yet. https://github.com/oca/

V 10 is quite supported by usable community module ports, and even still you will see here docs are still pointing at v8.0 OCA has ported most of the Connector series to 10 now. http://odoo-magento-connector.com/project/contribute.html.

OpenUpgrade is here: (See the Branch Structure). I have not yet used it but you can't use it till all your modules are ported and generally modules are "alive" at 10.0.... https://github.com/OCA/OpenUpgrade Their Branch structure goes back to V5 even.

I will do some testing. Just really hoping we can aim for 10 not 11.

Sorry for the trouble caused just in bringing up the subject (I do think I have been consistent on this subject).

Thank you for all your hard work! I know of the volume and the breadth of it.

Landis

From: "Jeremy Davis" notifications@github.com To: "DocCyblade/tkl-odoo" tkl-odoo@noreply.github.com Cc: "Landis Arnold" larnold@nomadic.net, "Mention" mention@noreply.github.com Sent: Sunday, May 13, 2018 6:30:27 PM Subject: Re: [DocCyblade/tkl-odoo] Odoo v10 for Turnkey (v14.2) (#78)

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

[ https://doc.therp.nl/openupgrade/ | 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/ | 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 | 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...)

— You are receiving this because you were mentioned. Reply to this email directly, [ https://github.com/DocCyblade/tkl-odoo/issues/78#issuecomment-388667655 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AFaR6AwjzoWqMgZwAp1ISRtIZ_DfcSUKks5tyNAjgaJpZM4OBwU3 | mute the thread ] .

l-arnold commented 6 years ago

From one other angle..

The OCA POS, Payment Terminal module has versions 8.0 and 10.0. This facilitates taking credit cards for selling actvities. https://apps.odoo.com/apps/modules/8.0/pos_payment_terminal/ The page also shows it available for version 10.

Yes complicated to get all the views, but the apps.odoo.com pretty much shows what is working in terms of additional modules.

Landis

From: "Landis Arnold" larnold@nomadic.net To: "DocCyblade" reply@reply.github.com Cc: "DocCyblade" tkl-odoo@noreply.github.com, "Mention" mention@noreply.github.com Sent: Sunday, May 13, 2018 7:41:46 PM Subject: Re: [DocCyblade/tkl-odoo] Odoo v10 for Turnkey (v14.2) (#78)

Jeremy and TKL Team, Sorry to even post this re Odoo but... In Github: https://github.com/odoo/odoo/branches/all?page=1

8.0 is still "Open" on Git even for updates. 7.0 and 6.1 are closed. 6.0, inextricably is "Open".

OpenUpgrade is "Active" on Branch 8, 9 and 10. Default is 11 but I don't know if it is "working" yet. Likely so but..

More important even to me: In terms of the Magento Connector which I rely upon very much (and the reason I wanted the Odoo Appliance in the first place) if you look at the Folder Structure of Branch 10 vs Branch 11 you will see very few folders in V 11. I really do not believe it is running in 11X I know it is running in version 10:

https://github.com/OCA/connector-magento/tree/10.0 https://github.com/OCA/connector-magento/tree/11.0 (the readme says it is running but there are nearly no folders in the Git for Branch 11)

There are several other important subjects, POS (Point of Sale) that are also critical for running a business. The same Equation holds. Look at the Folder Structure of branch 10 vs branch 11. 10 is built (see the sub modules in their folders -- ie credit card readers). https://github.com/OCA/pos/tree/10.0

nearly nothing in 11 https://github.com/OCA/pos/tree/11.0

We need to be able to process our orders, make our goods, and accept credit cards. That is doable now in Version 8 and Version 10 of Odoo. 11 is a stretch IMHO.

All for now. thank you for reading and all your hard work.

Landis

From: "Landis Arnold" larnold@nomadic.net To: "DocCyblade" reply@reply.github.com Cc: "DocCyblade" tkl-odoo@noreply.github.com, "Mention" mention@noreply.github.com Sent: Sunday, May 13, 2018 7:01:42 PM Subject: Re: [DocCyblade/tkl-odoo] Odoo v10 for Turnkey (v14.2) (#78)

Hi Jeremy, I know its a pain. I am turning my tkldev server back on. It will take a lot of old notes to get back to speed.

FYI though, EOL is not EOL in Odoo World. Many many people, businesses and developers are using Odoo 8 (9 and 10). OCB is a full Branch take on Odoo. It is only the "company" Odoo which is not supporting Odoo 8. ODoo are basically trying to force feed support.

Even still, https://github.com/odoo/odoo/branches/all Active work is being done on V 9 and V10 on Odoo, and Git is there going back to V6 on Odoo and V5 on OCA (Odoo Community Association). OCA is supporting Branches back to V 5 and

This is a good "reference" for what is really being supported and my view is that 11 is not really ported by the community yet. https://github.com/oca/

V 10 is quite supported by usable community module ports, and even still you will see here docs are still pointing at v8.0 OCA has ported most of the Connector series to 10 now. http://odoo-magento-connector.com/project/contribute.html.

OpenUpgrade is here: (See the Branch Structure). I have not yet used it but you can't use it till all your modules are ported and generally modules are "alive" at 10.0.... https://github.com/OCA/OpenUpgrade Their Branch structure goes back to V5 even.

I will do some testing. Just really hoping we can aim for 10 not 11.

Sorry for the trouble caused just in bringing up the subject (I do think I have been consistent on this subject).

Thank you for all your hard work! I know of the volume and the breadth of it.

Landis

From: "Jeremy Davis" notifications@github.com To: "DocCyblade/tkl-odoo" tkl-odoo@noreply.github.com Cc: "Landis Arnold" larnold@nomadic.net, "Mention" mention@noreply.github.com Sent: Sunday, May 13, 2018 6:30:27 PM Subject: Re: [DocCyblade/tkl-odoo] Odoo v10 for Turnkey (v14.2) (#78)

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

[ https://doc.therp.nl/openupgrade/ | 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/ | 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 | 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...)

— You are receiving this because you were mentioned. Reply to this email directly, [ https://github.com/DocCyblade/tkl-odoo/issues/78#issuecomment-388667655 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AFaR6AwjzoWqMgZwAp1ISRtIZ_DfcSUKks5tyNAjgaJpZM4OBwU3 | mute the thread ] .