Version Update mechanism

[GoogleCodeExporter]

Describe the aim of the proposed feature?
Every time we generate a new version that could alter the data structures and 
definition (mainly the objects / triggers / commands / reactions) the update is 
made manually by the user. In order to be user friendly an update mechanism is 
needed.
This update could be associated to a "new version available" feature, so the 
user just update the system when he wants and all core and data will be updated.

Describe how you would implement this feature
It must be splited in several concepts:

1) The developers must know that a change on the core has change the 
estructure, so a version updated is needed, they must adapt the update script 
to upgrade all structure.

2) A version check / upgrade mechanism must be create at core level, so it will 
be always check that the data has the correct version, if not suggest the user 
to upgrade the data manually or using the upgrading mechanism.

3) The plugins developers should be always check that the data that are 
including with the plugins match the correct version. To ensure that not plugin 
is published with missmatch version, the upload to marketplace mechanism should 
be reviewed to fail if the data is not compatible. A tool to upgrade the data 
could be created to help developers.

How much you feel this feature will be useful for the project?

[] Optional
[ ] Usefull
[ ] Can make the difference
[X] Necessary

Original issue reported on code.google.com by gabriel....@gmail.com on 10 Oct 2012 at 7:09

[GoogleCodeExporter]

Original comment by enrico.n...@gmail.com on 28 Oct 2012 at 6:37

• Changed state: Accepted

[GoogleCodeExporter]

assigned temporary to milestone 5.5 

Original comment by enrico.n...@gmail.com on 28 Oct 2012 at 7:12

• Added labels: Milestone-Release5.5