Tag releases

Question

Tag releases

rugk opened this issue 7 years ago · comments

rugk commented 7 years ago

Please tag your releases, so they can be seen on GitHub.

Currently we see "source" and "website", which is not useful and which also is not the way tags in git should be used.

Kate Ward · Answer 1 · Sat Sep 23 2017 19:43:57 GMT+0800 (China Standard Time)

Hi rugk,

Thank you for your feedback.

I agree that tags would be nice, and plan to use them going forward. Unfortunately, GitHub didn't support them when I imported shunit2 from SourceForge back in 2011 (support arrived in 2013), so none of my tags made it across. I tagged the v2.1.6 release by hand, but it references the full historical source (1.x version included), which isn't really ideal.

I also realize that the source isn't laid out to GitHub standards, but when I created shunit2 more than a decade ago, GitHub didn't exist. That said, I'll look into the GitHub best practices for supporting multiple versions simultaneously to see how to best restructure the codebase.

I'll leave this issue open until I've restructured things.

rugk · Answer 2 · Sat Sep 23 2017 20:08:54 GMT+0800 (China Standard Time)

GitHub didn't support them when I imported shunit2 from SourceForge back in 2011

I think it should work when you have a local copy with them. Just git push --tags.

And generally git tags do not have anything to do with GitHub. Also other source code hosting platforms use them.

Kate Ward · Answer 3 · Mon Sep 25 2017 02:36:39 GMT+0800 (China Standard Time)

Code is restructured. Active development will remain on the master branch, with all 2.0.x changes (likely none to follow) on the 2.0.x branch.

When I make a future 2.1.7 release, I will tag it appropriately.

Kate Ward · Answer 4 · Wed Jan 10 2018 07:11:29 GMT+0800 (China Standard Time)

2.1.7 release made and properly signed and tagged.
https://github.com/kward/shunit2/releases/tag/v2.1.7