Not sure if the dev team is familiar with this, but you can use git tag -a -m "tag related message" 1.4.3 to create a tagged release of a version (say 1.4.3) without duplicating the code base in subdirectories. The tag will be associated with a commit which also makes it easy to roll back to a specific version if needed and for users to find specific versions that they may need/want.
Not sure if the dev team is familiar with this, but you can use
git tag -a -m "tag related message" 1.4.3to create a tagged release of a version (say 1.4.3) without duplicating the code base in subdirectories. The tag will be associated with a commit which also makes it easy to roll back to a specific version if needed and for users to find specific versions that they may need/want.