Community mailing list archives
Re: Version 8, 9, ...by
You are right ERP need upgrades and it's not just a code update. It should be a migration project.
Issue is every year migrating and charging for the same not at all recommended. It's time consuming process.
1. Data migration
2. Custom Module Migration
3. Work flow and other configuration
4. Convincing users for changes and training
5. Verification of migrated data
6. Testing of new changes and signing off
It's not a one day job and same time not a high value project, because of existing customer relationship.
Our company dicided to stick on version 8 for some time and only new projects will be implemented in latest versions if it stable. And migration of existing customers to next version will be v 10 or v 11 after three or five years. Between this periods no miracle going to happen.
ERP not like a mobile app and not required a daily updates. Every year changing the core functionality of erp give a wring impression that product is not mature yet. Through version changes we expect only fixes and new modules.
And make minor and major versions
Minor version can be every year and major version should be every three or five years.
+ 971 55 66 77 001
Sent from Note III
2015-03-08 14:49 GMT-06:00 Luis Panozzo <email@example.com>:Odoo SA should be careful about the appropriate balance between alternatives. The real good thing is that OCA and the voice of the community are meaningful this time.Just a thought.IMHO, it is right!, just that no there are any "balance metter machine"! it is so subjecctive now between 7 - 8 - 9 we have too much more information in advance than before, that's a fact.Prepare a migration is a work that can be achieved in something like 1 year in a big implementation or less in little ones or more in more complex ones.Just to be sure everybody is talking about the same, and to avoid confuse people who beleive migrate an ERP enviromet is a simple job, that a migration represent only an apt-upgrade and that's it, in an ERP enviroment there are too mush things to considere and the technical part in only one of them, considere them all is avoid the right evolution, clean up the code and so on.If everybody is understand that, I think the timing to upgrade is a matter of decision, and a services that must generate income for all involved parts (Customer (receive features), Partner (Service opportunities), Community (more and better modules), Editor (revenue for the job done and more services)), if all parts receive what they need to continue growing up, the ecosystem is healthy and everybody wins.IMHO I feel we are so much better that at the begining, better enterprise prices, a more strong OCA everyday, better programmers comming to us, and more and more customers.Regards.----------------------