chipsalliance/Cores-VeeR-EH1

No tags for releases

robtaylor opened this issue · 5 comments

robtaylor commented

This makes it very hard to track what is considered aa released version!

agrobman commented

each release has a branch named as branch-1.X ..
master branch is latest release

robtaylor commented

I'm afraid that that doesn't help me know what the release is exactly. Also, only a small number of versions have a branch.

I would suggest a standard software-style release process of bumping the version in the .core file, readme, etc, and then tagging that point with "v(version number)", e.g v1.18.

aprnath commented

@robtaylor, actually all official releases (1.0 - 1.8) do have a branch. However your point is also valid regarding tag usage. We will look into this - maybe even consult with a person versed in "software-style" :-)

Thanks for the suggestion.

jrahmeh commented

Added tags v1.5, v1.6, v1.7, and v1.8

robtaylor commented