[Mesa-dev] [RFC] Mesa 17.3.x release problems and process improvements

Andres Gomez agomez at igalia.com
Tue Mar 27 10:17:05 UTC 2018


On Thu, 2018-03-22 at 09:46 +0100, Juan A. Suarez Romero wrote:
On Thu, 2018-03-22 at 00:28 +0000, Emil Velikov wrote:

[...]

> 
> > In detail:
> >  * make the patch queue, release date and blockers accessible at any
> >    point in time:

[...]

> > 
> >     * patches with trivial conflicts can be merged to the wip branch
> >       after another release manager, or patch author/reviewer has
> >       confirmed the changes.
> 
> I would change this to follow a more similar to current one: patches with
> trivial conflicts can be merged to the wip branch; author/reviewer will be
> notified asap about the new commit, that can be reviewed and, if required,
> requested to be modified/removed.
> 
> 
> This way, as trivial conflicts happen quite a few times, and indeed they are
> "trivial", we can enqueue them as we do not. The difference is that we warn the
> author quite soon, instead of waiting for the pre-announcement.

I agree with Juan.

-- 
Br,

Andres


More information about the mesa-dev mailing list