pc_man Posted November 18, 2008 Share Posted November 18, 2008 -Portability- Backwards compatibility is one of the key concepts of high-level programming. If we try to install new modules from 1.1beta1.2.3 or whatever version into the older ones, the module will not install correctly ( 80% from de modules will not install correctly ), the database from 1.0 into 1.1, etc... The code lacks upgradability a verry important feature to e-commmerce software...Maybe i want to upgrade just a few settings not all the base...impossible taskI know that there are thousand of hours involved...but a good software needs strong planning and restrictive rules.It is better to prevent chaos than it is to repair... Link to comment Share on other sites More sharing options...
jhnstcks Posted November 18, 2008 Share Posted November 18, 2008 If you could add the new modules from v1.1 into an older version, what would be the point of creating the new version? Link to comment Share on other sites More sharing options...
spott Posted November 18, 2008 Share Posted November 18, 2008 Version 1.1 is beta - so all modules for this - are also at beta stage. So I don't see here any problem. Link to comment Share on other sites More sharing options...
pc_man Posted November 18, 2008 Author Share Posted November 18, 2008 Portability for Presta or (self - portability) - use the code in a way that will be functional with the new and the older platform.1.0 version (stable)1.1 version ...is not a new version, is not a new base code with a new logic and refference, is 1.0 improved with some new things , that does not work with the older version.And if it is a completely NEW version...rename the version to 1.1 NEW - NO upgrade with older version. 1.2 the same and so on.The point is like this ... if you use today 1.0 version with your e-commerce modules and DB full with products like 2-3000 ...tomorrow you see 1.1 "stable" and you want to upgrade... how ?... reintroducing all your data again in the "new" version ? and next month will be 1.2... again a lot of work....please. Or you just want new features, like Wishlist..you need to change all for just one thing.Some of the modules can be modified to work in 1.0 ... but this is not the solution for mass use... if you want to adapt the "new" version with the older and vice-versa. Link to comment Share on other sites More sharing options...
spott Posted November 18, 2008 Share Posted November 18, 2008 You can upgrade from 1.0 to 1.1, but You can't take 1.1 parts and use them at 1.0 version. Link to comment Share on other sites More sharing options...
Damien Metzger Posted November 18, 2008 Share Posted November 18, 2008 We won't develop new deprecated modules :]Some of you really want the stats modules in the 1.0. But it's a whole new API that has been developed for them. So I'll tell you the same thing than jhnstcks: what would be the point of creating a new version? Link to comment Share on other sites More sharing options...
qasrani Posted May 27, 2009 Share Posted May 27, 2009 I would love to agree with Damien Metzger and jhnstcks if and only if, upgrading from one version to next is as easy as few clicks of mouse without getting involved into database and themes issues. Link to comment Share on other sites More sharing options...
qasrani Posted May 27, 2009 Share Posted May 27, 2009 Also if there is a STATS module given in backoffice of version 1.0 and written, COMING SOON, what is the idea of that when that module is certainly NOT coming for version 1.0? Link to comment Share on other sites More sharing options...
Recommended Posts