Hi Steffen,
thanks for bringing this up since it make sense if every team member
follows the same (or at least as similar) strategy.
On Tue, Nov 27, 2018 at 10:35:37AM +0100, Steffen Möller wrote:
> There are a few packages I once uploaded to our VCS that I know will not
> make it into a shape for them to be ready to be uploaded to our
> distribution. There are different reasons to that. Sometimes my focus has
> shifted away from it as a user. And at other times I found that it is too
> much work to e.g. get all Java dependencies into our distribution first. And
> there are packages for which I have just forgotten why the process has
> stalled. :o) And there are a few packages for which I could be motivated to
> complete the packaging, but would like to know if there is ongoing progress
> with the package by the uploader, not necessarily wanting to ask by email at
> an early stage screening our packages list.
>
> Should indicate how much the packaging has proceeded such that we could show
> that in our task list?
I think the best way to do so is to add a Remark field inside the tasks file.
> I have recently started to mention any issues in the
> debian/changelog file.
This is what I do usually in d/changelog:
* ...
TODO: what needs to be done
> Would it be preferable to have anything directly
> stated in the package description?
Rather not. As I said the Remark field exists and will seprately the
description of the software from some packaging information.
> Or should find a debian/TODO file be
> shown in our task pages/linked from there?
Probably also not the best idea. Just inventing another file and parsing
the data is something I'd consider overkill for a resolved problem (Remark
field).
Kind regards
Andreas.
--
http://fam-tille.de
