[Reproducible-builds] Too many repreoducible build emails? (was Re: [Pkg-haskell-maintainers] haskell-mime-mail status changed: reproducible -> FTBFS)

[Joachim Breitner]

Hi,

Am Dienstag, den 30.06.2015, 15:07 +0000 schrieb Mattia Rizzolo:
> On Tue, Jun 30, 2015 at 10:19:31AM +0100, Iain Lane wrote:
> > The Haskell team seems to get a *lot* of these emails, since it tends to
> > be that many of our packages change state (e.g. to and from FTBFS or get
> > fixed/broken) at the same time.
> 
> I also wonder how many (I don't dare checking!) email you got the last two days
> after the ghc 7.8 migration :)

well, that’s ok, as it should happen only oncen, and now all Haskell
package are of course reproducible in all future.

I have a different suggestion to remove the noise: Instead of having
three states (unreproducible, FTBFS, reproducible), you could have
four:
 * unreproducible
 * failing, previously unreproducible
 * failing, previously reproducible
 * reproducible

Then a mail should only be sent for state changes that involve a change
of reproducibility, and if a package in unstable goes from reproducible
to failing, previously reproducible to reproducible, no mails are sent
out. This makes sense: The r.d.n project is about reproducibility, not
about whether something is buildable or not.


Greetings
Joachim


-- 
-- 
Joachim "nomeata" Breitner
Debian Developer
  nomeata at debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nomeata at joachim-breitner.de | http://people.debian.org/~nomeata
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/reproducible-builds/attachments/20150705/4dd010aa/attachment.sig>