I've been thinking lately about how to improve my process
for making a release of one of the projects I work on.
Actually, calling it a process is to glorify it. Each of my
projects basically does things differently, but they do
share some common steps:
- Commit all changes, after they've been tested.
- Update README, NEWS, and maybe other documentation files
for the release.
- Create tarball.
- Put tarball somewhere under my public_html.
- If I have a Debian package of the project, update the
packaging, and build and test new version of package. Put
the resulting files also in public_html.
- Update the relevant web pages with version numbers,
links to tarball, etc.
- Announce, possibly on a mailing list, in my web log, or
on IRC.
- Maybe sign and upload the Debian packages to Debian.
That's a lot of tedious manual steps. I would like to
automate everything so that I only need a single command,
possibly excluding the upload to Debian. I have the
beginnings of script that does most of this, but it is not
very flexible. Actually, that's not true: I have several
scripts that overlap, and together they most of the above.
It's a bother to have to remember which script does what,
and is suitable for which project. They're all horrible to
improve upon.
I use
Bazaar (bzr)
for version control in all of my own projects. A couple of
days ago, I looked at the
builddeb
plugin for bzr, which creates a Debian package (source
and binary) from within a bzr branch. It doesn't do more
than that, however, and I'd like to do much more.
While thinking about this some more, I realized that
something tied to bzr isn't very appropriate. While I
currently favor bzr, I'd really like to not tie my
development processes too closely to it. If nothing else,
one of the projects I'm involved in is
piuparts,
which is currently maintained in Subversion, and I'd like to
use my automation for that as well.
Further, sometimes I package other people's software for
Debian. While most of the work is similar to when I package
my own software, there are some subtle differences, and
again, it'd be nice to use the same automation for this as
well.
And, finally, sometimes I work on fixing bugs in other
people's Debian packages, and most of the automation is
relevant to that work as well.
I've decided that a single, atomic command is not
acceptable. What I need is a suite of commands for each of
the small tasks, plus one or more scripts to combine them
together. The flexibility of combining small commands should
make it easy to adapt things for different workflows and
scenarios.
After some hacking, I came up with
Unperish. It's
currently in its early stages, but I intend to keep using it
and improving it, until it takes all the pain away from
making a release. At least for me, but hopefully it will be of
some use for other people.