Version management feature set questions
Couple of Q's on this feature:
We're a little confused why exactly there's a need for an account admin role to create new versions, seeing that version management is enabled per zone (not account)?
Also we're a little confused as to why you need to be an admin in the first place (rather than the Zone Versioning role) in the first place? Would it not make more sense to allow new versions to be created with a role with "less" permissions. seeing as you can't promote/rollback without the zone versioning role anyway.
And then separately, assuming you have developers working on two versions at the same time - is there an easy way of "merging" changes from the latest live zone into a version? Without it it makes concurrent development extremely challenging
Thanks so much!
We're a little confused why exactly there's a need for an account admin role to create new versions, seeing that version management is enabled per zone (not account)?
Also we're a little confused as to why you need to be an admin in the first place (rather than the Zone Versioning role) in the first place? Would it not make more sense to allow new versions to be created with a role with "less" permissions. seeing as you can't promote/rollback without the zone versioning role anyway.
And then separately, assuming you have developers working on two versions at the same time - is there an easy way of "merging" changes from the latest live zone into a version? Without it it makes concurrent development extremely challenging
Thanks so much!
