Community mailing list archives
Re: Version 8, 9, ...by
There are ERPs & Apps out there, created before year 2000, nothing change in CORE, even every monthly there are changes both on core side & module side
Hi christophe,<blockquote cite="mid:CAEFtrK=xSumFk4gqgh4tj+VwG89f0dfNx8KHDFF+scyHF0DemQ@mail.gmail.com" type="cite">
I perfectly agree with you.
Upgrades must be very careful and if in any way possible, backwards compatible.
So a module that works on an old version, should keep working on a newer one, with at most little adaptation.
On 09.03.2015 11:36, Christophe Hanon wrote:
Good topic,I think new releases are great as they bring new functionnalities, increase the scope of the product, give visibility and create more opportunities...
However I have a few (repeated) concerns:
1) Lost functionnalities e.: module recorder, ftp in doc management, user interface, gtk client, webkit,...
2) New stuff not very well documented, means producivity is weak, getting up to speed is hard. Btw thanks to c2c for writting a v8 programming guide...
3) Stabilisation (odoo + our own addons + community stuff) takes between 6 months to a year. So the stable-usage time is under a year -> too short.
4) Custom Code migration takes a lot of time (v5->v6 was simple, v6 to v.6.1 : piece of cake, 6.1 -> 7 - terrible, 7-> 8 pain again...
5) As a matter of fact we develop customization addons paid by customers, most of them are not willing to pay again and again for moving to new releases.
Because of this we start suffering from other ERP pain : customer not upgrading and keeping old software. So we end up maintaining more software code base and we loose again productivity and profitability.
I think, these are major area of improvements so integrator can be profitable.
On Sun, Mar 8, 2015 at 10:27 PM, Nhomar Hernández <firstname.lastname@example.org> wrote:
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.