[Debian-med-packaging] Bug#767238: unblock: camitk/3.4.0-1

[Nicolas SAUBAT]

Hello,

Thank you Andreas to have asked to unblock package CamiTK for version 3.4.0-1.

On 29/10/2014 21:52, Andreas Tille wrote:
> Hi,
> 
> On Wed, Oct 29, 2014 at 09:44:09PM +0100, intrigeri wrote:
>> Hi Andreas,
>>
>> Andreas Tille wrote (29 Oct 2014 14:17:27 GMT) :
>>> Here you can reas the reasons given by upstream why Debian should
>>> take over this well more tested version:
>>
>> It's good to know that upstream has expanded the scope of their
>> automated test suite. OTOH, considering the new release to be "more
>> tested" seems to be a little bit far-fetched, given it has not been
>> announced on the upstream website yet :)
> 
> Upstream in CC.
Indeed, I understand this point which could make us less credible :)

In fact, in the CamiTK team, we were considering fixing important bugs as a prerequisite of this release.
Our deadline was the Jessie freeze date. As he took us more time than the one we scheduled first to fix bugs, we decided to postpone announcing this version (and fix a bit more instead ;-) )
Now, our commits are freezed and we prepare to announce the 3.4.0 version on the CamiTK web pages. It would be online tomorrow at the latest!

Anyway, we understand our new version doesn't deal with security fixing or RC which explains the decision taken.
Thank you for your time,

Kind regards,
Nicolas.

> 
>> Additional info for whoever will make the decision:
>>
>>   * The version currently in testing has no bug known to Debian,
>>     except a wishlist one flagged as wontfix.
>>   * The debian/changelog entry for 3.4.0-1 doesn't close any bug.
>>   * Low popcon: 10 for libcamitk3.
>>
>>> as far as I understood no debdiff is needed for this request.
>>
>> My understanding of the freeze policy is different:
>> https://release.debian.org/jessie/freeze_policy.html
> 
> We are before Freeze and I was explicitly asked to follow
> 
>   https://lists.debian.org/debian-devel-announce/2014/10/msg00001.html
> 
> which says:
> 
>    You don't need to provide a debdiff
>    until the main freeze starts. 
> 
> I was refering to this statement and a debdiff does not make any sense
> when injecting a new upstream version.
> 
> Kind regards
> 
>         Andreas.
> 

-- 
Nicolas SAUBAT
Ingénieur Recherche et Développement
Equipe GMCAO - Laboratoire TIMC-IMAG
Pavillon Taillefer
Allée des Alpes - Domaine de la Merci
38706 La Tronche
Tel : (33)04 56 52 00 10