Tags and Version Bumps

[NP Hardass]

I briefly discussed this this Austin via IRC, and he recommended that I post it to this this, to get opinions from others in the group.

As many of you already know, git supports tags, which are most often used to mark a release for easy access in the future.  As a quick 5 second tutorial for those who aren't, git tag tagname; git push --tags

The Google Code interface supports tagging as seen here on another project: the git-core page, https://code.google.com/p/git-core/source/browse/.   Tags via git provide easy access download, either for the whole project, https://git-core.googlecode.com/archive/gitgui-0.19.0.tar.gz, or for a specific file, https://git-core.googlecode.com/git-history/gitgui-0.19.0/git-gui.sh.  In both of the of the previous examples, the tag was "gitgui-0.19.0."  Some projects opt to have "name-version", and others just "version.," but they can be whatever your project decides on.

This would allow users with push capability to author releases via tagging.  This also means that, if you concoct a serverside script for your website, you could grab the 5 most recent tags (or whatever you choose), and host links to them on the website, automating the process of releasing new versions.  Obviously, the server side scripts could do anything you wanted, ie downloading the latest tags and hosting them on the server, etc.  But the idea remains the same, I think that git tags would simplify your release workflow.

I'd be interested in your opinions, and I look forward to hopefully seeing you adopt this model in the future.  Thanks for your time.

--

NP-Hardass

[Dan Kegel]

I am a big believer in git tags, and I use them to trigger releases (sort of) in another project.

We'd need a buildbot to do it right.

And as long as we're talking process improvements, github seems to have a lower friction contributor workfow.

I'm pretty much a ghost at this point, but if I ever get a calm weekend where I'm not behind on everything, I'd love to set that all up.

- Dan

--
You received this message because you are subscribed to the Google Groups "winetricks-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to winetricks-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Austin English]

I'd love to see a move to github :)

That said, @Dan, I don't mind tagging stuff, I just thought it strange that I could tag but not push the release to winetricks.org. Do you have any ideas on ways that could happen, e.g., a cronjob on your box, I can give you a ssh key to update it, or something else. But I'd like to avoid having months old releases on there, because we keep getting bugs filed that are fixed, but their distros are running the 'latest winetricks'.

--

-Austin

[Dan Kegel]

It's partly a permissions thing - winetricks.org is just a bump on the side of a larger site,

and shares passwords.  But I could make it a mirror of a github download area...

[Austin English]

Could you script pulling tags that are pushed to the current repo, until a github repo is made?

[Dan Kegel]

I think you're asking for a buildbot that does automatic releases, yes?

[Austin English]

That's the ideal, yes. My goal is to not have winetricks.org lag months behind.

[NP Hardass]

I'm not sure that I understand why a buildbot is necessary.  git/src/winetricks is file that you'd want users to download, so if you ran git tag winetricks-20150101, ang git push --tags, then you'd be able to download with https://winetricks.googlecode.com/git-history/winetricks-20150101/winetricks.  No buildbot necessary.  (Unless I'm missing something)