Live data from Hacker News

Releases – a workflow for shipping software to end users

github.com

41–50 of 82 posts

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

#41
post #3

Cool! We finally have downloads back! It looks like this fails on tag names that have a slash in them.

That was my first thought when I saw this. It seems even more strange they discontinued it only to revive it with changes they could have just iterated through with new features/changes like this release.

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

#42

Earlier quoted context omitted.

With their recent $100mm round, they might be working on this already. Could lead to an interesting future of software selling/piracy, where those that will buy, buy, and those that are desperate not to can git clone make clean; make install

I've already seen a number of apps in the Mac App Store that take this exact approach. Two examples off the top of my head: Textual, an IRC client [1, 2] Blink, a SIP client [3, 4]...this is pretty difficult to compile, though... ----- [1] https://itunes.apple.com/us/app/textual/id403012667 [2] https://github.com/Codeux/Textual [3] https://itunes.apple.com/us/app/blink-lite/id431473881 [4] http://icanblink.com/downlo…

Cyberduck, an FTP client, takes a similar (though easier) approach. You can buy it on the Mac App Store for $23.99 [0], get precompiled binaries for free on their website [1], or grab the source yourself [2].

[0]: https://itunes.apple.com/us/app/cyberduck/id409222199 [1]: http://cyberduck.ch [2]: https://trac.cyberduck.ch/browser

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

#43

This sounds like the death of SourceForge. (I know, you could argue that it's already dead, and also argue that it's very much alive)

Schrödinger's source code repository?

Only if no body checks to see if it is still alive (used by anyone), which in this case would kind of kill it.

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

#44
post #42

Earlier quoted context omitted.

I've already seen a number of apps in the Mac App Store that take this exact approach. Two examples off the top of my head: Textual, an IRC client [1, 2] Blink, a SIP client [3, 4]...this is pretty difficult to compile, though... ----- [1] https://itunes.apple.com/us/app/textual/id403012667 [2] https://github.com/Codeux/Textual [3] https://itunes.apple.com/us/app/blink-lite/id431473881 [4] http://icanblink.com/downlo…

Cyberduck, an FTP client, takes a similar (though easier) approach. You can buy it on the Mac App Store for $23.99 [0], get precompiled binaries for free on their website [1], or grab the source yourself [2]. [0]: https://itunes.apple.com/us/app/cyberduck/id409222199 [1]: http://cyberduck.ch [2]: https://trac.cyberduck.ch/browser

[deleted]

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

#45
post #24
post #20

Is there any way to add the release notes via a git commit? This is very nice, but it introduces further dependence on GitHub if something like that isn't possible. I suppose as long as there's API access someone could / will write an exporter, though. Anyway, great stuff either way!

Agree - would be awesome if the release notes were stored as part of the git repo, and editable from anywhere.

You should probably commit your release notes as a file in the repository before tagging the release, then just copy-paste them into the github "release" - that way anyone who gets the source tarball from anywhere also gets the release notes.

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

#47
post #44
post #42

Earlier quoted context omitted.

Cyberduck, an FTP client, takes a similar (though easier) approach. You can buy it on the Mac App Store for $23.99 [0], get precompiled binaries for free on their website [1], or grab the source yourself [2]. [0]: https://itunes.apple.com/us/app/cyberduck/id409222199 [1]: http://cyberduck.ch [2]: https://trac.cyberduck.ch/browser

[deleted]

Do you have any data / references to support this?

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

#48
post #46

Excited for this! No more view raw and save.

Why would you ever do that instead of just download as zip or clone?

For JavaScript or CSS single-file projects it's actually quite simpler to wget the one file from the Raw URL (or copy-paste the contents into a new buffer in your editor), than to clone/download the archive and then move the file from the downloaded directory and then clean up the other downloaded files.

edit For example, `curl https://raw.github.com/documentcloud/backbone/master/backbon... > js/lib/backbone-min.js`

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

#49

Earlier quoted context omitted.

With their recent $100mm round, they might be working on this already. Could lead to an interesting future of software selling/piracy, where those that will buy, buy, and those that are desperate not to can git clone make clean; make install

I've already seen a number of apps in the Mac App Store that take this exact approach. Two examples off the top of my head: Textual, an IRC client [1, 2] Blink, a SIP client [3, 4]...this is pretty difficult to compile, though... ----- [1] https://itunes.apple.com/us/app/textual/id403012667 [2] https://github.com/Codeux/Textual [3] https://itunes.apple.com/us/app/blink-lite/id431473881 [4] http://icanblink.com/downlo…

I never thought about it like that. I bought Textual because I wanted to support the developers.

The benefit of it being open-source was that I could try it, use it, and hack it, before deciding they'd done a damn good job.

Post reply on HN