[Pkg-clamav-devel] Preparing for 0.94.1

[Stephen Gran]

This one time, at band camp, Michael Tautschnig said:
> Hi all,
> 
> I was just trying to find out what to do to prepare a release of 0.94.1. I don't
> yet feel too comfortable with the workflow, so just let me try to sketch it
> here:
> 
> - Get a git remote ref to ssh://git.debian.org/git/users/sgran/clamav-devel
> - Do git merge clamav-devel/tags/clamav-0.94.1 (actually it seems that this one
>   doesn't exist in the clamav-devel git repository yet!?)

The tags don't usually appear in their svn tree for at least several
hours after release.  I've spoken with upstream, and they have promised
to address it more quickly in future (read, hopefully this one)
releases.

> - Download upstream's tarball and verify that everything had actually made its
>   way into their subversion repository
> - The usual round of BTS checks (actually, in this case, also looking into the
>   staged version of rc1 in git is worthwhile)
> - Anything else? pristine-tar and etch-volatile may need work; what actually is
>   pristine-tar good for? Should we try to get this release into etch-volatile?

pristine-tar stores an xdelta for the tarball in the repo against a git
checkin.  What this means in practical terms is that, in exchange for
the 14k or so of xdelta storage, you get to keep the tarball in git.
This means everyone gets access to it quickly instead of having to also
download the tarball in addition to the git repo.  Joey Hess is truly a
god among men.

Yes, I think targetting etch-volatile is a good idea as well - certainly
most people using clamav on stable in any serious way are using it from
volatile, judging by the bug reports.

I think that overall, you have outlined the important parts of the
workflow.  The few things missed out are things like checking for new
config options (I'm fairly sure one has been introduced this time, but
debian/rules should FTBFS rather than let a new one slip by - the main
problem is when an option is dropped, it's harder to catch without
upgrade testing).  Also, I usually run icheck over the old libclamav.h
and the new to make sure no major changes have slipped in without
appropriate changes to the packaging - Debian has caught at least one
accidental soname change that was necessary that upstream missed.

Cheers,
-- 
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        sgran at debian.org |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-clamav-devel/attachments/20081104/3f4a1b3a/attachment.pgp