Should we send Travis messages to ghc-builds?

[Ben Gamari]

Ben Gamari <ben at smart-cactus.org> writes:

> [ Unknown signature status ]
>
> Hello everyone,
>
> While picking up the pieces from a failed merge today I realized that we
> currently spend a fair bit of carbon footprint and CPU cycles making
> Travis test GHC yet the results of these tests aren't pushed anywhere.
>
> Would anyone object to having Travis push notifications of changes in
> red/green state to ghc-builds at haskell.org? Perhaps this will allow some
> of us to react more quickly to regressions.
>
Actually Thomas points out that we indeed used to do this and yet
stopped because it meant that users would fork the repository, enable
Travis build on their fork, and then inadvertantly spam the list. So,
perhaps we shouldn't do this.

- Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 472 bytes
Desc: not available
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20160721/19757bd0/attachment-0001.sig>