Bug#767238: unblock: camitk/3.4.0-1
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/msg1.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 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54525627.80...@imag.fr
Bug#767238: unblock: camitk/3.4.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package camitk Here you can reas the reasons given by upstream why Debian should take over this well more tested version: - Forwarded message from Nicolas SAUBAT nicolas.sau...@imag.fr - Date: Wed, 29 Oct 2014 10:50:33 +0100 From: Nicolas SAUBAT nicolas.sau...@imag.fr To: debian-...@lists.debian.org Subject: Re: CamiTK 3.4.0 packaging This CamiTK release has a much better test suite (with over 190 integration tests), which improves the QA compared to the previous release. All tests are now enabled in d/rules. The new CamiTK version 3.4.0 features improvements for the user, mainly on image handling, which is, according to us essential in the medical field: - Improved DICOM support (still using the C++ library of Mathieu Malaterre, already packaged in Debian[1]). We think a good reading of DICOM images is important. - Support for any image position / orientation in 3D space, information read from medical scanners[2]. - New service Frame, which allows to refer a component position relatively to any other component, in 3D space. This feature has mainly been requested in the medical robotic field. Also, to increase software stability, we improved our bug solving policy, by increasing our automatic tests number (which has an impact on the number of tests run during the packaging task) and using a new bug tracking system[3]. Regarding the Debian packaging process, we think this new version of CamiTK, in addition to its new features, is more stable. As Emmanuel said, we increased the number of test run after configuration - compilation up to 191 (compared to less than 20 tests done in the packaging of the 3.3.2 version). Also, we updated the tests done by autopkgtest (debian/tests), after installation of the package. These ones expect more information in the 3.4 version than the previous 3.3.x versions. Finally, it took us a bit time for this last packaging, as we tested our software in order to solve important bugs before releasing it. We apologize if it's a bit late for integrating this new version in Jessie, but we understand the migration process, and we'll follow your decision. Thanks again, Regards, Nicolas [1] https://packages.qa.debian.org/g/gdcm.html [2] https://forge.imag.fr/plugins/mediawiki/wiki/camitk/index.php/Images_orientation_in_CamiTK [3] https://bugzilla-timc.imag.fr/ - End forwarded message - -- (include/attach the debdiff against the package in testing) as far as I understood no debdiff is needed for this request. unblock camitk/3.4.0-1 -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141029141727.28157.38130.report...@mail.an3as.eu
Bug#767238: unblock: camitk/3.4.0-1
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 :) 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 Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/85y4ryy5ba@boum.org
Bug#767238: unblock: camitk/3.4.0-1
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. 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/msg1.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. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141029205206.gb1...@an3as.eu
Bug#767238: unblock: camitk/3.4.0-1
Hi Niels, On Wed, Oct 29, 2014 at 09:20:27PM +0100, Niels Thykier wrote: Control: tags -1 wontfix On 2014-10-29 15:17, Andreas Tille wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package camitk Here you can reas the reasons given by upstream why Debian should take over this well more tested version: [... embedded mail ...] Hi Andreas, Sorry, but I will have to decline your request for an unblock of camitk/3.4.0-1. Sadly, the changes between the current version of camitk in testing and camitk/3.4.0-1 are /not/ compatible with our freeze guidelines. I might have missunderstood the announcement[1]. Can you give an example case when asking for reducing the testing migration time to 5 days is appropriate? While I certainly appreciate many of the arguments (especially the focus on more automated testing and it coming from upstream), we did set a deadline for including arbitrary changes and your upload of camitk/3.4.0-1 seems to have missed said deadline. I'm aware that we missed the deadline for a 10 day migration. I obviously missed the point of the announcement[1]. Sorry about this but some clarification would be great. Kind regards Andreas. [1] https://lists.debian.org/debian-devel-announce/2014/10/msg1.html -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141029205903.gc1...@an3as.eu
Bug#767238: unblock: camitk/3.4.0-1
Andreas Tille wrote (29 Oct 2014 20:52:06 GMT) : We are before Freeze and I was explicitly asked to follow [...] Thanks :) -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/854mumwpsv@boum.org
Bug#767238: unblock: camitk/3.4.0-1
On 2014-10-29 21:59, Andreas Tille wrote: [...] Hi Andreas, Sorry, but I will have to decline your request for an unblock of camitk/3.4.0-1. Sadly, the changes between the current version of camitk in testing and camitk/3.4.0-1 are /not/ compatible with our freeze guidelines. I might have missunderstood the announcement[1]. Can you give an example case when asking for reducing the testing migration time to 5 days is appropriate? Certainly. It was primarily intended for security fixes or (to some extend) RC bugs, where a forced 10-day migration would/might do more harm than good. While I certainly appreciate many of the arguments (especially the focus on more automated testing and it coming from upstream), we did set a deadline for including arbitrary changes and your upload of camitk/3.4.0-1 seems to have missed said deadline. I'm aware that we missed the deadline for a 10 day migration. I obviously missed the point of the announcement[1]. Sorry about this but some clarification would be great. Kind regards Andreas. [1] https://lists.debian.org/debian-devel-announce/2014/10/msg1.html I hope you found it the example clarifying. ~Niels -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54515867.4090...@thykier.net
