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

On 5 April 2018 at 03:33, Ilia Mirkin wrote: > On Wed, Apr 4, 2018 at 12:12 PM, Emil Velikov > wrote: >> On 22 March 2018 at 00:39, Ilia Mirkin wrote: >>> Just one bit of feedback, for the rest I either agree or have no

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

On Wed, 2018-04-04 at 11:27 -0700, Mark Janes wrote: > "Juan A. Suarez Romero" writes: > > > On Wed, 2018-04-04 at 10:07 -0700, Mark Janes wrote: > > > Emil Velikov writes: > > > > In detail: > > > > * make the patch queue, release date and

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

On Wed, Apr 4, 2018 at 12:12 PM, Emil Velikov wrote: > On 22 March 2018 at 00:39, Ilia Mirkin wrote: >> Just one bit of feedback, for the rest I either agree or have no opinion: >> >> On Wed, Mar 21, 2018 at 8:28 PM, Emil Velikov

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

"Juan A. Suarez Romero" writes: > On Wed, 2018-04-04 at 10:07 -0700, Mark Janes wrote: >> Emil Velikov writes: >> > In detail: >> > * make the patch queue, release date and blockers accessible at any >> >point in time: >> > * queued

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

On Wed, 2018-04-04 at 10:07 -0700, Mark Janes wrote: > Emil Velikov writes: > > > Hi all, > > > > Having gone through the thread a few times, I believe it can be > > summarised as follows: > > * Greater transparency is needed. > > * Subsystem/team maintainers. > > *

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

Emil Velikov writes: > Hi all, > > Having gone through the thread a few times, I believe it can be > summarised as follows: > * Greater transparency is needed. > * Subsystem/team maintainers. > * Unfit and late nominations. > * Developers/everyone should be more

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

On 22 March 2018 at 00:39, Ilia Mirkin wrote: > Just one bit of feedback, for the rest I either agree or have no opinion: > > On Wed, Mar 21, 2018 at 8:28 PM, Emil Velikov > wrote: >> * unfit and late nominations: >> * any rejections that are

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

On Thu, 2018-03-22 at 16:24 -0700, Dylan Baker wrote: > Quoting Ilia Mirkin (2018-03-22 15:16:18) > > On Thu, Mar 22, 2018 at 6:00 PM, Dylan Baker wrote: > > > Quoting Ilia Mirkin (2018-03-21 17:39:14) > > > > Just one bit of feedback, for the rest I either agree or have no

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

On Thu, 2018-03-22 at 09:46 +0100, Juan A. Suarez Romero wrote: On Thu, 2018-03-22 at 00:28 +, Emil Velikov wrote: [...] > > > In detail: > > * make the patch queue, release date and blockers accessible at any > >point in time: [...] > > > > * patches with trivial conflicts can

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

Quoting Ilia Mirkin (2018-03-22 15:16:18) > On Thu, Mar 22, 2018 at 6:00 PM, Dylan Baker wrote: > > Quoting Ilia Mirkin (2018-03-21 17:39:14) > >> Just one bit of feedback, for the rest I either agree or have no opinion: > >> > >> On Wed, Mar 21, 2018 at 8:28 PM, Emil Velikov

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

On Thu, Mar 22, 2018 at 6:00 PM, Dylan Baker wrote: > Quoting Ilia Mirkin (2018-03-21 17:39:14) >> Just one bit of feedback, for the rest I either agree or have no opinion: >> >> On Wed, Mar 21, 2018 at 8:28 PM, Emil Velikov >> wrote: >> > * unfit

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

Quoting Ilia Mirkin (2018-03-21 17:39:14) > Just one bit of feedback, for the rest I either agree or have no opinion: > > On Wed, Mar 21, 2018 at 8:28 PM, Emil Velikov > wrote: > > * unfit and late nominations: > > * any rejections that are unfit based on the

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

On Thu, 2018-03-22 at 00:28 +, Emil Velikov wrote: > Hi all, > > Having gone through the thread a few times, I believe it can be > summarised as follows: > * Greater transparency is needed. > * Subsystem/team maintainers. > * Unfit and late nominations. > * Developers/everyone should be

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

Just one bit of feedback, for the rest I either agree or have no opinion: On Wed, Mar 21, 2018 at 8:28 PM, Emil Velikov wrote: > * unfit and late nominations: > * any rejections that are unfit based on the existing criteria can > be merged as long as: >

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

Hi all, Having gone through the thread a few times, I believe it can be summarised as follows: * Greater transparency is needed. * Subsystem/team maintainers. * Unfit and late nominations. * Developers/everyone should be more involved. * Greater automation must be explored. NOTES: * Some

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

On Mon, 2018-03-12 at 15:48 +, Emil Velikov wrote: > On 12 March 2018 at 14:20, Andres Gomez wrote: [...] > > On Tue, 2018-03-06 at 19:34 +, Emil Velikov wrote: > > > > [...] > > > > > A few other ideas that were also came to mind: > > > > > > - Round robin -

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

Timothy Arceri writes: > I'd just like to point out that as an outside user of Intels CI I have > missed regressions on a couple of occasions. However this was not due to > "Lazy behaviour", having a CI system is fantastic and I'm very grateful > to have access to it.

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

On 14/03/18 07:36, Mark Janes wrote: Daniel Vetter writes: On Tue, Mar 13, 2018 at 4:46 PM, Mark Janes wrote: Daniel Vetter writes: On Mon, Mar 12, 2018 at 11:54:45PM -0700, Kenneth Graunke wrote: On Friday, March 9, 2018

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

Daniel Vetter writes: > On Tue, Mar 13, 2018 at 4:46 PM, Mark Janes wrote: >> Daniel Vetter writes: >> >>> On Mon, Mar 12, 2018 at 11:54:45PM -0700, Kenneth Graunke wrote: On Friday, March 9, 2018 12:12:28 PM PDT Mark Janes wrote:

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

Kenneth Graunke writes: > [ Unknown signature status ] > On Friday, March 9, 2018 12:12:28 PM PDT Mark Janes wrote: > [snip] >> I've been doing this for Intel. Developers are on the hook to fix their >> bugs, but you can't make them do it. They have many pressures on

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

On Tue, Mar 13, 2018 at 4:46 PM, Mark Janes wrote: > Daniel Vetter writes: > >> On Mon, Mar 12, 2018 at 11:54:45PM -0700, Kenneth Graunke wrote: >>> On Friday, March 9, 2018 12:12:28 PM PDT Mark Janes wrote: >>> [snip] >>> > I've been doing this for

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

Daniel Vetter writes: > On Mon, Mar 12, 2018 at 11:54:45PM -0700, Kenneth Graunke wrote: >> On Friday, March 9, 2018 12:12:28 PM PDT Mark Janes wrote: >> [snip] >> > I've been doing this for Intel. Developers are on the hook to fix their >> > bugs, but you can't make them do

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

On Mon, Mar 12, 2018 at 11:54:45PM -0700, Kenneth Graunke wrote: > On Friday, March 9, 2018 12:12:28 PM PDT Mark Janes wrote: > [snip] > > I've been doing this for Intel. Developers are on the hook to fix their > > bugs, but you can't make them do it. They have many pressures on them, > > and a

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

Kenneth Graunke writes: > On Friday, March 9, 2018 12:12:28 PM PDT Mark Janes wrote: > [snip] >> I've been doing this for Intel. Developers are on the hook to fix their >> bugs, but you can't make them do it. They have many pressures on them, >> and a maintainer can't

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

On Friday, March 9, 2018 12:12:28 PM PDT Mark Janes wrote: [snip] > I've been doing this for Intel. Developers are on the hook to fix their > bugs, but you can't make them do it. They have many pressures on them, > and a maintainer can't make the call as to whether a rendering bug is > more

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

Quoting Mark Janes (2018-03-12 14:59:29) > Dylan Baker writes: > > > Quoting Mark Janes (2018-03-12 12:40:47) > >> Handling a screw-up could be done by maintainers by force-pushing the > >> commits off the WIP branch, and adding some annotations that prevent the > >> broken

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

Dylan Baker writes: > Quoting Mark Janes (2018-03-12 12:40:47) >> Handling a screw-up could be done by maintainers by force-pushing the >> commits off the WIP branch, and adding some annotations that prevent the >> broken commit from being re-applied to WIP by automation. >>

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

Quoting Mark Janes (2018-03-12 12:40:47) > Dylan Baker writes: > > > Quoting Emil Velikov (2018-03-12 08:38:31) > >> On 12 March 2018 at 11:31, Juan A. Suarez Romero > >> wrote: > >> > On Fri, 2018-03-09 at 12:12 -0800, Mark Janes wrote: > >> >> Ilia

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

Emil Velikov writes: > On 12 March 2018 at 11:31, Juan A. Suarez Romero wrote: >> On Fri, 2018-03-09 at 12:12 -0800, Mark Janes wrote: >>> - Patches are applied to proposed stable branch by automation when the >>>associated commit is pushed to

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

Dylan Baker writes: > Quoting Emil Velikov (2018-03-12 08:38:31) >> On 12 March 2018 at 11:31, Juan A. Suarez Romero wrote: >> > On Fri, 2018-03-09 at 12:12 -0800, Mark Janes wrote: >> >> Ilia Mirkin writes: >> >> >> >> > On Tue,

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

Quoting Emil Velikov (2018-03-12 08:38:31) > On 12 March 2018 at 11:31, Juan A. Suarez Romero wrote: > > On Fri, 2018-03-09 at 12:12 -0800, Mark Janes wrote: > >> Ilia Mirkin writes: > >> > >> > On Tue, Mar 6, 2018 at 2:34 PM, Emil Velikov

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

On 12 March 2018 at 14:20, Andres Gomez wrote: > Thanks for opening this thread Emil. > > I will open new branches for other topics that have been boiling in our > minds for a while. I hope you, Emil, can forgive us for not having been > more diligent with those, as you are

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

On 12 March 2018 at 11:31, Juan A. Suarez Romero wrote: > On Fri, 2018-03-09 at 12:12 -0800, Mark Janes wrote: >> Ilia Mirkin writes: >> >> > On Tue, Mar 6, 2018 at 2:34 PM, Emil Velikov >> > wrote: >> > > So while others

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

On Mon, 2018-03-12 at 07:30 -0700, Mark Janes wrote: > "Juan A. Suarez Romero" writes: > > > On Fri, 2018-03-09 at 12:12 -0800, Mark Janes wrote: > > > Ilia Mirkin writes: > > > > > > > On Tue, Mar 6, 2018 at 2:34 PM, Emil Velikov

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

"Juan A. Suarez Romero" writes: > On Fri, 2018-03-09 at 12:12 -0800, Mark Janes wrote: >> Ilia Mirkin writes: >> >> > On Tue, Mar 6, 2018 at 2:34 PM, Emil Velikov >> > wrote: >> > > So while others explore ways of improving

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

Thanks for opening this thread Emil. I will open new branches for other topics that have been boiling in our minds for a while. I hope you, Emil, can forgive us for not having been more diligent with those, as you are already aware of some of them ...  On Tue, 2018-03-06 at 19:34 +, Emil

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

Hi Juan, On 12 March 2018 at 12:10, Juan A. Suarez Romero wrote: > On Mon, 2018-03-12 at 11:49 +, Daniel Stone wrote: >> On 12 March 2018 at 11:31, Juan A. Suarez Romero wrote: >> > We are improving this by moving to use Gitlab CI (still wip), which

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

Thanks Mark for bringing this thread to my attention by Ccing me ☺ I'll try to be brief and just comment inline. On Fri, 2018-03-09 at 12:12 -0800, Mark Janes wrote: > Ilia Mirkin writes: > > > On Tue, Mar 6, 2018 at 2:34 PM, Emil Velikov > >

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

Hi Ilia, On 6 March 2018 at 20:09, Ilia Mirkin wrote: > On Tue, Mar 6, 2018 at 2:34 PM, Emil Velikov wrote: >> So while others explore ways of improving the testing, let me propose >> a few ideas for improving the actual releasing process. >> >>

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

On Mon, 2018-03-12 at 11:49 +, Daniel Stone wrote: > Hi Juan, > > On 12 March 2018 at 11:31, Juan A. Suarez Romero wrote: > > On Fri, 2018-03-09 at 12:12 -0800, Mark Janes wrote: > > > Ilia Mirkin writes: > > > - CI Automation immediately

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

Hi Juan, On 12 March 2018 at 11:31, Juan A. Suarez Romero wrote: > On Fri, 2018-03-09 at 12:12 -0800, Mark Janes wrote: >> Ilia Mirkin writes: >> - CI Automation immediately builds/tests the proposed stable branch >>whenever it changes. Release

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

On Fri, 2018-03-09 at 12:12 -0800, Mark Janes wrote: > Ilia Mirkin writes: > > > On Tue, Mar 6, 2018 at 2:34 PM, Emil Velikov > > wrote: > > > So while others explore ways of improving the testing, let me propose > > > a few ideas for improving

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

Ilia Mirkin writes: > On Tue, Mar 6, 2018 at 2:34 PM, Emil Velikov wrote: >> So while others explore ways of improving the testing, let me propose >> a few ideas for improving the actual releasing process. >> >> >> - Making the current state

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

On Tue, Mar 6, 2018 at 2:34 PM, Emil Velikov wrote: > So while others explore ways of improving the testing, let me propose > a few ideas for improving the actual releasing process. > > > - Making the current state always visible - have a web page, git >branch and

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

Hi Ken, all, As you may know, a few Mesa 17.3.x releases went out with some nasty bugs. Some were due to lack of basic coverage, while others required fairly complex test setups. Ones that are currently not available or feasible in an automated manner. Additionally, with the increased pace of