Live data from Hacker News

Releases – a workflow for shipping software to end users

github.com

81–82 of 82 posts

Re: Releases – a workflow for shipping software to end users

#81
post #74

Earlier quoted context omitted.

We thought the Downloads feature was doing more harm than good in its previous form. Quality-wise it just wasn't up to snuff (failed frequently, flash, lack of design). Bad experiences on the site need to be fixed or killed. No one was willing to dedicate time to fixing it because they felt their time was better spent on other things so that left killing it. The timing of the Releases feature only entered into the de…

Huh? This one requires flash too AFAICT!

I sought and got clarification from Github. The Flash is only for copy-to-clipboard functionality. Not related to Releases.

Re: Releases – a workflow for shipping software to end users

#82
I see a problem with the current implementation: Releases are auto-generated from git tags. That means all tags you'll ever use on your repo will be auto-exposed as "release", even if the tag reads "dead_end_implementing_foo" or "before_major_rewrite". Tags are an implementors' tool, releases belong to product management. I want to be able to control my releases, so at least be able to delete auto-generated ones (without losing the git tag).
Post reply on HN