Re: [Caml-list] Doing compiler patch review with a dedicated mailing-list

["François Bobot" <francois.bobot@cea.fr>]

On 13/01/2014 10:04, Adrien Nader wrote:
> On Sat, Jan 11, 2014, Simon Cruanes wrote:
>> Le Sat, 11 Jan 2014, Adrien Nader a écrit :
>>> Hi,
>>>
>>> (and sorry for the mail sent a few minutes ago :) )
>>>
>>> I'd like to know what people think about having a mailing-list for
>>> reviews and tests of patches to the compiler and tools around it.
>>>
>>> The idea is to do something similar to the kernel mailing-list. I mostly
>>> like mantis and it is possible to attach files but it becomes fairly
>>> unreadable after a while. The audience is also mostly limited to people
>>> who are subscribed to the bug report. I hope this reduces the work and
>>> burden of reviewers and especially commiters.
>>>
>>> The goal is not to replace patches on mantis and you shouldn't believe
>>> this has been blessed by the core development team (nor mentionned to
>>> them actually). Instead, I hope this helps do quicker (and smaller?)
>>> iteration of patches.
>>>

I don't know how you generate and _manage_ patches with svn. Indeed the 
linux kernel developers never used svn with their mailing-list review 
workflow and developed git for simplifying this workflow.

It seems counterproductive to have more than one place for discussing 
one thing so I think the developers must make a choice:
- keeping patch review in mantis
- going to a mailing-list review workflow and moving from svn
- going to a merge-request workflow on github, specific gitlab instance, 
bitbuckets, ...

The last two points have the benefit to allow to easily comment inside 
the patches.

The third point (at least on github) subsume the second point since you 
can answer to github issues or merge-requests by email. You can also ask 
to be notified for every issues or merge-requests of a project.

Best,

-- 
François