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 opinion:
>>>
>>> On Wed, Mar 21, 2018 at 8:28 PM, Emil Velikov
>>> wrote:
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 blockers accessible at any
> > > >point in time:
>
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
>> wrote:
>>> * unfit and late nominations:
>>> * any reject
"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 patches can be accessed, via a branch - say wip/17.3,
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.
> > * Unfit and late nominations
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 involved.
> * Greater automat
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 unfit based on the existing criteria can
>>
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
> > > > opinion:
> > >
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 b
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
> >> wrote:
> >> >
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 and late nominations:
>> > * any rejections
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 existing criteria can
> >
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 mo
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:
>* subsystem specific patc
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 o
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 - where me/Igalia team wil
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. However, it's not uncommo
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 12:12:28 PM PDT Mark Janes wrote:
[snip]
I've been doing this for
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:
[snip]
> I've been doing this for Intel. Develop
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 them,
>> and a maintainer c
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 Intel. Developers are on the hook to fix their
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 it. They have many
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 m
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 make the call as to whethe
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 impor
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 commit from being re-a
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.
>>
>
> That sounds like
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 Mirkin writes:
> >> >>
> >> >> > On Tue, Ma
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 master. The existing commit message
>>>ann
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, Mar 6, 2018 at 2:34 PM, Emil Velikov
>> >> > wrote:
>> >> > > S
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
> >> > wrote:
> >> > > So while others explore ways of
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 already aware of some o
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 explore ways of improving the testing, let me propose
>> > > a few ideas
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
> > > > wrote:
> > > > > So while others explore ways of impro
"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 the testing, let me propose
>> > > a few ideas for improving the actu
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 Vel
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 allows
>> > us to
>> > run the testing pr
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
> > wrote:
> > > So while others explore ways of impro
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.
>>
>>
>> - Making the current state always visible - ha
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 builds/tests the proposed stable branch
> > >whe
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 managers verify the results.
>>
>
> This is k
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 the actual releasing process.
> > >
> > >
> > >
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 always visible - have a web page, git
>>branch an
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 other ways for people to see
44 matches
Mail list logo
