nvme-cli release naming strategy

[Keith Busch]

On Fri, Nov 12, 2021 at 04:49:37PM +0100, Daniel Wagner wrote:
> Hi Keith,
> 
> I was thinking on how we want to handle releases with
> the master and  nvme-cli-monolithic branch. I think it
> would make sense  to rename  nvme-cli-monolitic to
> something v1.x and  keep it maintained for a while alife.
> 
> And the master would be marked as v2.x. This would
> avoid a flag day release which we force to switch
> the users from monolithic version to the splited
> version.
> 
> What do you think?

Yep, I was thinking the same thing: once we feel the master branch is
stable with the backend library split from the command line utility, we
should start a new v2.x version naming. If there's any reason to make a
release on the old one in the meantime (I had to tag one yesterday due
to an unfortunate bug in v1.15), that branch can continue using the v1.x
names.