----- Original Message -----
From: "Dan Callaghan" <dcallagh(a)redhat.com>
To: "Amit Saha" <asaha(a)redhat.com>
Cc: "Beaker development" <beaker-devel(a)lists.fedorahosted.org>
Sent: Friday, November 15, 2013 4:09:55 PM
Subject: Re: [Beaker-devel] GitHub releases for peripheral/related projects
Excerpts from Amit Saha's message of 2013-11-15 16:02:19 +1000:
> While thinking of how to go about writing Beah's release notes, it came to
> my mind
> that why don't we use GitHub release feature for that? [1]
>
> What I have in mind is once we are done with the tagging, GitHub has a
> zip/.tar.gz
> ready. We could use GitHub's Web UI to do the entire release process and
> have
> a link from the beah docs.
>
> I have zero experience with using this GitHub feature. They also have an
> API.
> So perhaps, we can do all of it with a script.
>
> Thoughts? If this sounds encouraging, I could give it a shot and also we
> can adopt it for
> our other projects.
We don't publish beah or rhts tarballs *anywhere* right now, so having
them on GitHub would certainly be an improvement. But I would rather we
just put them in
http://beaker-project.org/releases/ alongside the
beaker tarballs.
Okay, so how does this sound:
1. Tag a new release
2. "Announce" a release using the Web UI
3. Get the tarballs from the GitHub repo and simply scp them to the above URL
4. Link the GitHub release announcement from the Beah docs and link to the tarballs
above.
Perhaps the whole thing can be automated with the help of [1].
[1]
http://developer.github.com/v3/repos/releases/
Thoughts?
-Amit.
--
Dan Callaghan <dcallagh(a)redhat.com>
Software Engineer, Infrastructure Engineering and Development
Red Hat, Inc.
--
Amit Saha <
http://echorand.me>
Infrastructure Engineering and Development
Red Hat, Inc.