Dear devs,
I updated diagrams about "Github PR", especially page 11:
GHC development flow
http://takenobu-hs.github.io/downloads/ghc_development_flow.pdf
https://github.com/takenobu-hs/ghc-development-flow
Please teach me if I have misunderstood.
Regards,
Takenobu
2016-11-04 7:36
Takenobu Tani writes:
> Hi devs,
>
> 2016-10-31 20:02 GMT+09:00 Takenobu Tani :
>
>> > Also it might be good to add something about the process of fixing doc
>> "bugs" and improving the doc.
>> >
>> > I think these are areas where less experienced
Hi devs,
2016-10-31 20:02 GMT+09:00 Takenobu Tani :
> > Also it might be good to add something about the process of fixing doc
> "bugs" and improving the doc.
> >
> > I think these are areas where less experienced Haskell developers can
> add value and contribute to the
>
Hi George,
2016-10-30 21:49 GMT+09:00 George Colpitts :
> Thanks for writing this up. A small suggestion, for the box "Add a test
case"
> it might be good to add a reference to
> https://ghc.haskell.org/trac/ghc/wiki/Building/RunningTests/Adding
Thank you for advice.
A
Hi Takenobu
Thanks for writing this up. A small suggestion, for the box "Add a test
case" it might be good to add a reference to
https://ghc.haskell.org/trac/ghc/wiki/Building/RunningTests/Adding
Also it might be good to add something about the process of fixing doc
"bugs" and improving the doc.
Hi Ben, Joachim and devs,
I updated the following:
* page 7: update "committer flow" to "direct commit"
* page 9: add a simple diagram for the various ticket states
* page 10: update ghc-proposals flow
* page 13: correct "Arcanist"
* page 13: add "travis"
Here is Rev.2016-Oct-30:
GHC
Hi Ben, Joachim,
2016-10-30 2:07 GMT+09:00 Ben Gamari :
> Nope, that's exactly right. Unfortunately, even "trivial" fixes have a
> tendency to break the tree (which has been happening too often recently)
> so I'm trying to push contributors to use CI whenever possible.
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 :
> > > There is a box „committer flow“. What exactly is meant by that? Is
> > > there more to be said about that?
> > >
> > I think this means
Takenobu Tani writes:
> Hi Ben, Joachim,
>
> 2016-10-29 1:36 GMT+09:00 Ben Gamari :
>> > 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
Hi Ben, Joachim,
2016-10-29 1:36 GMT+09:00 Ben Gamari :
> > 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.
Joachim Breitner writes:
> Hi,
>
> Am Freitag, den 28.10.2016, 21:19 +0900 schrieb Takenobu Tani:
>> For myself and new contributors, I drew overview pictures about GHC
>> development flow.
>>
>> GHC development flow
>>
Hi Ben, Joachim,
Thank you for your checking and reply!
After I'll be carefully considered, and then reply.
I'll reflect your feedback.
Please wait for a little while.
Thank you very much :) ,
Takenobu
2016-10-28 22:01 GMT+09:00 Ben Gamari :
> Takenobu Tani
Hi,
Am Freitag, den 28.10.2016, 21:19 +0900 schrieb Takenobu Tani:
> For myself and new contributors, I drew overview pictures about GHC
> development flow.
>
> GHC development flow
> http://takenobu-hs.github.io/downloads/ghc_development_flow.pdf
>
13 matches
Mail list logo