Michael Pasternak has posted comments on this change. Change subject: core: change default storage format to V3 ......................................................................
Patch Set 1: > 1. will new features be available in both? absolutely, also developers will be implementing new feature only once in api they want it to be available from, e.g: v1: available in api >= v1 vN: available in api >=vN (in future i guess first case will become less interesting) > 2. when you say "won't provide backward compatibility" I assume you mean in > corner cases, not all around? i mean parameters/signatures, not necessary functionality, i.e if you have deprecated signature in v1, it won't be available in api > v1 > 3. how will sdk/cli support both versions? sdk per api, cli is self-learning and can work with any sdk, no changes requiered -- To view, visit http://gerrit.ovirt.org/17782 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I257510ce479cc7e068a50e3610df3baffc6444d8 Gerrit-PatchSet: 1 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Alissa Bonas <abo...@redhat.com> Gerrit-Reviewer: Alissa Bonas <abo...@redhat.com> Gerrit-Reviewer: Allon Mureinik <amure...@redhat.com> Gerrit-Reviewer: Daniel Erez <de...@redhat.com> Gerrit-Reviewer: Itamar Heim <ih...@redhat.com> Gerrit-Reviewer: Maor Lipchuk <mlipc...@redhat.com> Gerrit-Reviewer: Michael Pasternak <mpast...@redhat.com> Gerrit-Reviewer: automat...@ovirt.org Gerrit-Reviewer: oVirt Jenkins CI Server Gerrit-HasComments: No _______________________________________________ Engine-patches mailing list Engine-patches@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-patches
