Change to parallel versions?

[wsnyder]

The current repo is organized with a tag for each version, as this allows for easier comparison and merging etc.

It looks like most vendors distribute UVM with a directory for each version, so that a single checkout can be used by different projects' versions with appropriate subdirectory pointers.

Should we switch? Likely we'd want to make a new repo and deprecate this one to avoid breaking old code.

Alternatively we could have a submodule for each version, pointing at different tags in the same base repository, but I suspect this will confuse all but the most serious git users ;)

@kbieganski, thoughts?

[kbieganski]

If the purpose of this repo is to have users clone it and use it for their projects with Verilator, then for sure we should switch to what you propose.
If Verilator is to come with UVM 'out of the box' then it doesn't matter that much, and setting up UVM should happen behind the scenes. make install could checkout UVM several times at different tags.

I guess another argument in favor of reorganizing is having an always up-to-date and more informative readme, no matter what version you're at. Also, we could still want to do some workarounds across all UVM versions, even if we don't need any for UVM 2017 right now.

So on balance, I agree we should switch.