Hi Ole As upstream maintainer, I admit to being a bit confused: we agreed to move maintenance to the Debian Science Team, but then watched as skimage was dropped from testing. If the team does not take responsibility for keeping the package up to date, who is ultimately responsible?
Thank you very much for helping with the maintenance and packaging of the scikit-image package. We so appreciate all your efforts! Best regards Stéfan On Tue, Oct 17, 2017, at 00:42, Ole Streicher wrote: > Source: skimage > Version: 0.13.1-1 > Severity: important > X-Debbugs-Cc: debian-scie...@lists.debian.org, deb...@onerussian.com > > Hi Yaroslav, > > skimage was under Debian Science Team maintenance since the bugfixes > just before the freeze of Stretch, and I think the move was done with > your agreement. This was accompanied with a change of the repository to > > https://anonscm.debian.org/git/debian-science/packages/skimage.git > > Is there a reason why you move it back to personal maintenance, ignore > all changes in between and switch back to the upstream repository? > > If that was on error, please rebase your changes to the alioth > repository. Otherwise, I would ask you to give a rationale for the > change. > > The reason for having it team maintained is as always: give other team > members the possibility to submit changes and do an upload, and also to > keep a common repository. That worked well, as proven before the Stretch > freeze, and also in between (there was an upload by Mattia Rizolo, and > Andreas Tille also provided some changes). > > Best regards > > Ole >
