Please create/push tags
Opened this issue · 5 comments
https://rubygems.org/gems/systemu refers to this repo as the source of truth, but looking at the repository I can't easily determine the delta between 2.6.4 and 2.6.5.
Could you please tag revisions and push those tags, so folks can at at least look at the commits between two releases in leiu of a changelog.
While you are right on needing a change log (and I will attempt to remedy this in the future), systemu gets less than 10 commits per year , the whole GitHub commit list is 55 entries and this is entirely due to the stability of the library (meaning that we can reasonably expect the trend to continue).
So you will understand I hope that this not high in the priority list 😄
Apart from the way I had to reduce #41 was to install the gem twice and diff between two installed versions and then poke around for a commit in the git annotate.
I'd prefer changelogs and tags, but I can get by on the master repo having tags and reflecting the version I could download from rubygems (the Rakefile and systemu.gemspec in master aren't current - https://gist.github.com/richardc/b70fa7f5ed0d60d1fb1c)
Without wanting to sound pedantic (and failing miserably) next time, try the commit list first and check merge commits. It makes figuring the diff out much, much easier.
You're making my point for me. With tags I'd know where to start and stop reading. Can you honestly say you can tell that 2.6.5 has been shipped and what's in it by looking at this? https://github.com/ahoward/systemu/commits/47f55145454c702bfad999ca81e5ffeabd828527
You're asking the wrong person (which is why we're having this discussion).
My answer is 'hell, yeah!' but then again I know the code inside out and I'm used to reading Ruby and working on GitHub, which means I can't really be the judge on how easy it is to figure out the changes.
So I appreciate the input and by the next iteration (which might be in a year) we'll take steps to make it clearer. Still, low prio 😉