Seems we have agreed on increasing minor version of UI markup to 2.1.
I've updated
https://blueprints.launchpad.net/murano/+spec/dynamic-ui-specify-no-explicit-name-field
On Thu, Jul 10, 2014 at 1:08 AM, Timur Sufiev tsuf...@mirantis.com wrote:
Also agree with Stan.
I'd like to refrain from
Also agree with Stan.
I'd like to refrain from bumping version to the next integer each time some
change is done to the markup format. It's quite a small change after all,
also big numbers in format's version imply that it's changed every friday
and should not be relied on.
08.07.2014 22:10
Hi guys!
I agreed with Stan suggestion. We also need to track somewhere in the
documentation for mapping between the Murano version and Dynamic UI version.
BTW, what about to keep version values in integer, so the next one would be
3?
Regards, Kate.
On Sun, Jul 6, 2014 at 4:21 PM, Stan Lagun
I we increment version to say 2.1 we could add code to dashboard to check
for markup version and if it encounters version 2.0 to print verbose error
telling how to migrate markup to 2.1.
I don't see how both version can be supported simulteniously but at lease
Version attribute must be checked and
Hi, folks!
Recently we had decided to change a bit how Murano's dynamic UI works,
namely do not explicitly specify 'name' field in first 'Add
Application' form, but add it here automatically, since every
component in Murano has a name. To avoid confusion with the 'name'
field added by hand to the
