[Pkg-clamav-devel] Freeze Exception for 0.93.3?

[Scott Kitterman]

On Sun, 24 Aug 2008 16:40:35 +0200 Michael Tautschnig <mt at debian.org> wrote:
>> What are your thoughts on how far we go to keep Clamav up to date in 
Lenny?  
>> 
>> In Ubuntu we've pushed rather hard to release with an up to date clamav 
when 
>> it's a point release that doesn't break rdepends (I recognize that the 
Ubuntu 
>> style is rather more forward leaning on these kinds of issues, so it's 
not 
>> directly relevant).  
>> 
>> I would think 0.93.3 would be a good thing to have a freeze exception 
for.  
>> The only new clamav bug since we updated our development release to 
0.93.3 
>> I've seen in Ubuntu was one complaint about a typo in a man page.
>> 
>
>Will clamav be tied to the release process at all? That is, we have
>volatile.d.o, but are we going to put the package in lenny as well? It 
will be
>outdated soonish anyway...

I think it needs to be in Lenny if for no other reason than rdepends.  
Every single libclamav rdepend in Etch will not work with the volatile 
packages.  So if the move is to volatile, then it's have to be more than 
clamav that moves.

For reference, in Ubuntu we took rather the opposite aproach.  Ubuntu has 
no Volatile equivalent and its backports are official.  So we put 
everything (i.e. with all the rdepends that needed changing) in Ubuntu 
Backports and then after extended testing moved them all into the release 
as updates.  I was able to coordinate this effort across a 4 supported 
releases.  It worked out well (broke one custom app used by one person due 
to functionality being dropped from python-clamav and once I explained the 
benifits of the newer clamav, he wasn't even upset).

This does ask me to wonder if this team should be for clamav or clamav and 
rdepends?  If the rdepends were under team maintnenace that would certainly 
ease transitions.

Scott K