Call for Discussion: New Project: Skara -- investigating source code management options for the JDK sources
patrick at reini.net
Mon Jul 30 21:00:11 UTC 2018
> Am 30.07.2018 um 12:26 schrieb Mario Torre <neugens at redhat.com>:
>> +1 on that. With a simple email-based review process (plus webrevs hosted on
>> cr.o.j.n) I can easily scan dozens of incoming changes to see if they may be
>> something I need to dive more deeply into. That is all lost if reviews
>> happens inside some other system - even if a notification email is generated
>> when such reviews are initiated.
>> Changes to the review processes/tools should be kept a separate as possible
>> from the selection of an underlying SCM.
> Yes, my point exactly, I can live with git if that's the consensus,
> but not with a GitHub style process.
That’s exactly what I tried to point out also in my statement earlier. For me there is Git as SCM
and work flow handling as Github provides for example (which seems for me does not fit for
the OpenJDK kind of workflow)
More information about the discuss