On 04/11/22 12:36, Richard W.M. Jones wrote:
On Mon, Apr 11, 2022 at 12:34:30PM +0200, Laszlo Ersek wrote:
> On 04/11/22 12:11, Richard W.M. Jones wrote:
>> I'd like to remove the unused -o json mode. The implementation is
>> over-complicated and the only potential user (KubeVirt) isn't using it
>> now and would be better off with a proper -o kubevirt mode, which I'm
>> going to implement later.
>>
>> My plan would be to add the patches in two stages. The first patch,
>> which only removes the documentation but leaves the feature and test,
>> would be applied to stable branch virt-v2v 2.0. The second patch
>> would be go on the development branch 2.1 (which hasn't yet been
>> created). The first stable release without this feature would be 2.2.
>
> If the second patch goes on the 2.1 dev branch, then why wouldn't the
> 2.1 release include it? (IOW the 2.1 release would not have "-o json"
> any more.)
Just sticking to the convention so far that 2.x for odd x are
development releases. We don't care about maintaining backwards
compatibility during the development cycle.
OK -- so 2.1 will contain the patch (it will not have "-o json"), it's
just that we don't call 2.1 a "stable" release.
Thanks for explaining!
Laszlo