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)
Releases – a workflow for shipping software to end users
21–30 of 82 posts
Re: Releases – a workflow for shipping software to end users
#22It would be amazing to have public Releases from a private repo.
+1 - I would LOVE this feature.
Re: Releases – a workflow for shipping software to end users
#23Is 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!
The article claims that releases are structured around git tags. A git tag can be accompanied by a message which is shown on the releases page. In that sense, it doesn't depend on Github.
Re: Releases – a workflow for shipping software to end users
#24Is 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.
Re: Releases – a workflow for shipping software to end users
#25Is 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!
The article claims that releases are structured around git tags. A git tag can be accompanied by a message which is shown on the releases page. In that sense, it doesn't depend on Github.
I'm not sure it's using tag annotations; I'm not seeing evidence of them. Plus, if I clone a repo with releases, then push (with tags) to a new repo, the new repo doesn't have any of the release notes.
Re: Releases – a workflow for shipping software to end users
#26While on the subject: does anyone know a software/service for automating software releases? I usually perform these steps manually: create a new tag, merge the “next” branch into the “master” branch, run “make dist” from a clean checkout, do a handful of sanity checks on the result, gpg-sign it, push it into a separate git repository for the website, archive the current docs in the website, update the website’s docs…
jenkins or any other of the continuous integration solutions
Yes, but that normally involves lots of inline-shell-scripting and connecting a wide array of plugins together. It's not exactly a stream-lined process.
Re: Releases – a workflow for shipping software to end users
#27While on the subject: does anyone know a software/service for automating software releases? I usually perform these steps manually: create a new tag, merge the “next” branch into the “master” branch, run “make dist” from a clean checkout, do a handful of sanity checks on the result, gpg-sign it, push it into a separate git repository for the website, archive the current docs in the website, update the website’s docs…
the maven-release-plugin is wonderful for this, and integrates nicely with Jenkins
Re: Releases – a workflow for shipping software to end users
#28Earlier quoted context omitted.
The article claims that releases are structured around git tags. A git tag can be accompanied by a message which is shown on the releases page. In that sense, it doesn't depend on Github.
I'm not sure it's using tag annotations; I'm not seeing evidence of them. Plus, if I clone a repo with releases, then push (with tags) to a new repo, the new repo doesn't have any of the release notes.
Weird. I'm seeing some evidence of my tag annotations, but the first parts are cut off and I don't see a way to view all of them. Maybe they are still getting the kinks worked out...
Re: Releases – a workflow for shipping software to end users
#29I just had a glimpse of a wonderful future where GitHub releases a payments system, packaging options, and suddenly becomes an ideal app store ecosystem.
Re: Releases – a workflow for shipping software to end users
#30While on the subject: does anyone know a software/service for automating software releases? I usually perform these steps manually: create a new tag, merge the “next” branch into the “master” branch, run “make dist” from a clean checkout, do a handful of sanity checks on the result, gpg-sign it, push it into a separate git repository for the website, archive the current docs in the website, update the website’s docs…
the maven-release-plugin is wonderful for this, and integrates nicely with Jenkins
I use the release plugin myself on almost all my projects, but--BUT--it needs to be said that it's not very flexible. If you can't live with the way it's setup to do things, you're better off writing a shell script to automate things your way than trying to bend the release plugin to fit your needs.