On Sat, Oct 20, 2018 at 11:08 AM Charles R Harris
wrote:
>
>
> On Fri, Oct 19, 2018 at 2:10 PM Ralf Gommers
> wrote:
>
>>
>>
>> On Fri, Oct 19, 2018 at 4:49 PM Stephan Hoyer wrote:
>>
>>>
>>>
>>> On Fri, Oct 19, 2018 at 2:22 AM Sebastian Berg <
>>> sebast...@sipsolutions.net> wrote:
>>>
On
On Fri, Oct 19, 2018 at 2:10 PM Ralf Gommers wrote:
>
>
> On Fri, Oct 19, 2018 at 4:49 PM Stephan Hoyer wrote:
>
>>
>>
>> On Fri, Oct 19, 2018 at 2:22 AM Sebastian Berg <
>> sebast...@sipsolutions.net> wrote:
>>
>>> On Fri, 2018-10-19 at 11:02 +0300, Matti Picus wrote:
>>> > We currently have hi
On Fri, Oct 19, 2018 at 4:49 PM Stephan Hoyer wrote:
>
>
> On Fri, Oct 19, 2018 at 2:22 AM Sebastian Berg
> wrote:
>
>> On Fri, 2018-10-19 at 11:02 +0300, Matti Picus wrote:
>> > We currently have highest, high, normal, low, and lowest priority
>> > labels
>> > for github issues/PRs. At the rece
On Fri, Oct 19, 2018 at 2:22 AM Sebastian Berg
wrote:
> On Fri, 2018-10-19 at 11:02 +0300, Matti Picus wrote:
> > We currently have highest, high, normal, low, and lowest priority
> > labels
> > for github issues/PRs. At the recent status meeting, we proposed
> > consolidating these to a single "
On Fri, 2018-10-19 at 11:02 +0300, Matti Picus wrote:
> We currently have highest, high, normal, low, and lowest priority
> labels
> for github issues/PRs. At the recent status meeting, we proposed
> consolidating these to a single "high" priority label. Anything
> "low"
> priority should be mer