On Friday, 26 July 2013 at 22:37, Vishwanathan Krishnamoorthy wrote:
>
> ok thanks for the clarification, so manifest_version is specifically for the
> properties in the manifest and not the capabilities of the runtime.
>
> What triggers a version change? I can think of
> 1) modification to an existing property
> 2) Adding new properties
>
> 2 is fine but 1) IMO would break backward compatibility and would require app
> developers to maintain multiple versions of the app
>
Yeah, we shouldn't need to do 1), hopefully (fingers crossed, knock on wood!).
But the option is always there if we _really_ need to. Even in case 2, we would
only need a version change if the new property actually affected the runtime:
consider, I don't think "description" is used by Gaia, is it? So stuff that we
add just to support the store can be safely added to any version and is simply
ignored by the runtime without affecting users.
_______________________________________________
dev-webapps mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-webapps
