I cloned both the master branch and the 4.3.6 branch to my machine, to be able to switch from a Plone 5 or a Plone 4.3.6 environment. When I "vagrant up" the second one, vagrant complains that it cannot change the VM name to plonedev.
That seems to be because the Vagrantfile specifies the "plonedev" name for both branches.
I suggest that the specific version, before creating the branch or tag, should specifiy the name for the VM as something like "plonedev-4.3.6". Therefore they all can coexist, without needing of changing the Vagrantfile (which should be de plonedev.vagrant develeopers realm) or killing one of the machines to bring up the another.
Or maybe (I don't know vagrant enough to know if it is possible) adding a prompt for the VM name, if that is easier to implement.
I cloned both the master branch and the 4.3.6 branch to my machine, to be able to switch from a Plone 5 or a Plone 4.3.6 environment. When I "vagrant up" the second one, vagrant complains that it cannot change the VM name to plonedev.
That seems to be because the Vagrantfile specifies the "plonedev" name for both branches.
I suggest that the specific version, before creating the branch or tag, should specifiy the name for the VM as something like "plonedev-4.3.6". Therefore they all can coexist, without needing of changing the Vagrantfile (which should be de plonedev.vagrant develeopers realm) or killing one of the machines to bring up the another.
Or maybe (I don't know vagrant enough to know if it is possible) adding a prompt for the VM name, if that is easier to implement.