simple pictures about GHC development flow

[Joachim Breitner]

Hi,

Am Samstag, den 29.10.2016, 21:36 +0900 schrieb Takenobu Tani:
> Hi Ben, Joachim,

> > 2016-10-29 1:36 GMT+09:00 Ben Gamari <ben at smart-cactus.org>:
> > > There is a box „committer flow“. What exactly is meant by that? Is
> > > there more to be said about that?
> > >
> > I think this means someone with commit bits simply pushing a patch
> > without submitting to code review. Ideally we'd be able to deprecate
> > this workflow in favor of the "auto-validating push" that you've
> > proposed.
> 
> I assumed that "committer flow" is simply pushing a patch without
> submitting to code review or without discussion.
> I thought committers [1] have the authority in case of typo or small
> modification.
> Do I misunderstand?

I see. The term “flow” suggested something deeper or more structured
(which might be good, but is not the case). Maybe relabel it “direct
commit”.

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
  mail at joachim-breitner.de • https://www.joachim-breitner.de/
  XMPP: nomeata at joachim-breitner.de • OpenPGP-Key: 0xF0FBF51F
  Debian Developer: nomeata at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20161029/65669f0a/attachment.sig>