Community mailing list archives
Re: Migration strategy for new API (v8 and higher)by
What Raphael said. If it touches partner, product, stock or accounting then it pretty much needs at least one rewrite anyway from 6.1 to 9.
OH yeah and reports, fun times.
On Sat, 14 Nov 2015 8:27 PM Jay Vora <email@example.com> wrote:
We have been doing some v8 and some v9(from v6 and from v7).It is very difficult, but yes luckily v8 has been fine. bt v9 migration still seems dark.On Fri, Nov 13, 2015 at 6:52 PM, zahid jalal <firstname.lastname@example.org> wrote:+1 @Raphaël.Hello Ferdinand,frankly I think it's way too complex. Moreover stock changed totally in v8 and accounting changed totally in v9. At the end of the day most of your modules would need to be totally re-designed between v7 and v9 so keeping API compatibility is a minor concern in this. Better focus your energy on migrating IMHO.Hi I would prefer to add v8 API compatibility to 6.1 (or 7). This would allow to write new modules with the new syntax and rewrite and test existing module by module - especially these modules which are not affected by design changes in later versions. Has anyone done something like that or has anyone an idea how complex this is? Most of the code must be almost there as in v8 the API backward compatibility is implemented. Or do I miss something regards Ferdinand--
_______________________________________________--The Splendid journey of 2 years in Numbers---
<img src="cid:email@example.com" style="color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
Serpent Consulting Services Pvt. Ltd.
Web : http://www.serpentcs.com
Mobile : 91 - 9879354457Twitter: jaynvora
Blog : http://jayvora.blogspot.com