On Fri, Oct 16, 2015 at 01:40:22PM +0200, Jérémy Bobbio wrote:
> I would say that it's better to keep any issue which other free software
> projects might bump into.

Agreed.

> I know it's far from a clear guideline. In any
> cases, we have the history, as Holger said.

I'd like to avoid having to recover an old issue from git history, if
possible.

So I propose this simple guideline to remove issues: Do it only when
they were due to bugs in our CI.

For example, I was going to add an issue like this:

hardlink_becomes_regular_file
  hardlinks in build1 become regular files in build2

but in the end I decided that it was better to reschedule the affected
packages. This issue was probably an artifact of disorderfs, and it is
an example of the kind of issue that I would consider safe to remove
(or even desirable, for cleanup).

_______________________________________________
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Reply via email to