View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003326 | OXID eShop (all versions) | 2.3. Extensions (modules, themes) | public | 2011-10-24 09:15 | 2012-12-10 13:33 |
| Reporter | marco_steinhaeuser | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Product Version | 4.5.3 revision 39087 | ||||
| Summary | 0003326: Version number of themes shall be changed | ||||
| Description | The version number of Azure is still 0.5 although massive changes have been made since 4.5.0. Define a process how to change theme version numbers when changes happen to it. | ||||
| Tags | No tags attached. | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
| related to | 0004513 | resolved | saulius.stasiukaitis | Theme Version Azure need to change from 1.2 to 1.3 |
|
|
Version 1.2 in 4.6 beta ;-) |
|
|
Decision is: change the number of version if there was any change during the development of new version. There is agreement, that we can do template changes in the Patches. That would mean that theme version would be changed each Minor version release (like 1.2, then 1.3, 1.4, etc.). If in any version we would change more generic part of theme - like structure of files system, etc. - then Major digit would be changed, like 2.0. |
