[ghc-steering-committee] Deadlines for Shepherds?

[Simon Marlow]

Just sent an email about the -Wall proposal. Thanks for the reminder!

On 5 January 2018 at 21:06, Joachim Breitner <mail at joachim-breitner.de>
wrote:

> Hi,
>
> you know that I like slim smooth processes with not too many rules, and
> our current process worked pretty nicely for the first few proposals.
> But now it seems that we lost some steam, and a fair number of
> proposals are stuck waiting for their Shepherd to make progress.
>
> Does this mean that people simply need deadlines for work to be done?
>
> Do you want deadlines?
>
>
> Also, I am happy to re-assign some stalled proposals to new shepherds.
> Does anyone want to volunteer recommending a decision for one or more
> of these proposals:
>
> Lazy unboxed tuples
> https://github.com/ghc-proposals/ghc-proposals/pull/35
>
> Mutable constructor fields
> https://github.com/ghc-proposals/ghc-proposals/pull/8
>
> Deprecate STM invariant mechanism
> https://github.com/ghc-proposals/ghc-proposals/pull/77
>
> -Wall to include incomplete-uni-patterns and incomplete-record-updates
> https://github.com/ghc-proposals/ghc-proposals/pull/71
>
> Thanks,
> Joachim
>
> --
> Joachim Breitner
>   mail at joachim-breitner.de
>   http://www.joachim-breitner.de/
>
> _______________________________________________
> ghc-steering-committee mailing list
> ghc-steering-committee at haskell.org
> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20180108/f857e322/attachment.html>