Hi,

Very interesting topic, btw. 
And I would like to hear more opinions about that, especially from those, which 
do support for several (or much more) shops and need to keep that up-to-date 
(means invest lot of time and money for updating to latest version).
So - do you prefer to invest more into updates between Patches, but by doing 
that also automatically get more stable shop, or description about fixes in 
bugtrack comments are enough for you and you can choose which one of those to 
apply. 
From our side it also hard to keep that line, esp. after release of new 
versions (Minor or Major - x.y.0). Anyway, up until now we had the goal to keep 
the Patches as simple to update as possible, in perfect case - just copy the 
changed source code files over existing ones and that's all. Also we assume, 
that each (even simple) fix in templates is very expensive to apply in end-shop 
because you need to do that manually. And if you need to update tens of shops - 
that takes time...

So we are interested in your opinion about that, to know if we are wrong in 
assuming some part.


Best regards,
Dainius Bigelis





-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Frank Zunderer
Sent: Wednesday, February 06, 2013 5:37 PM
To: [email protected]
Subject: [oxid-dev-general] Template Changes in Minor Versions

Hi all,

while answering a forum post i stumbled across this bug: 
https://bugs.oxid-esales.com/view.php?id=4240

This is not resolved in current version because: "as this does require template 
changes, we will release it only in 5.1. For earlier versions please use this 
fix ..."

I understand the policy not to do template changes in minor versions, i don’t 
think this is a good policy though. The reason not to change templates is this:
"Except for important bug fixes, we usually don’t do any template changes in 
patches. This makes your life much easier when patching an existing OXID eShop."

Well I would think this is an important bug fix as selection lists are not 
usable without it.

Even if not, bugs in Templates are a different story than changing folder 
structure, variable names, method calls etc. No one benefits from not releasing 
bugfixes in Templates. Contrary, this makes life not easier but harder because 
in order to have a fully functional shop you would have to keep track of all 
solved but not yet released template bugs and fix them yourself. I think this 
policy needs to be rethought.

Regards,
Frank Zunderer

_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

Reply via email to