Excerpts from Amit Saha's message of 2013-11-15 16:19:37 +1000:
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?
I think we need release notes ("announcements") in the beah docs, not
just on GitHub, otherwise we are locked in to GitHub's proprietary
release process.
All it needs is a new page "Changes" or "Release Notes" in the beah
sphinx book, with a new entry added each time a new version is tagged.
The process should just look like:
vim documentation/release-notes.rst
git add documentation/release-notes.rst
tito tag
git push origin master beah-123
# some magic here to get the tarball published under
#
http://beaker-project.org/releases/
--
Dan Callaghan <dcallagh(a)redhat.com>
Software Engineer, Infrastructure Engineering and Development
Red Hat, Inc.