+1 to letting conjunctions form naturally.
In the bikeshedding discusion:
That would mean I'm biased to having the reduced label set to have reduced
colours for the general category.
Eg. SDK colour, Runner colour, beam resources colour, and IO being it's own
special unique colour, and awaiting
I like that idea (and the list) as well.
On Tue, Dec 6, 2022 at 1:59 PM Kerry Donny-Clark wrote:
> I really like the idea of multi-select and automatic "awaiting triage".
> Kenn, I think the list you have looks good to me.
>
> On Tue, Dec 6, 2022 at 1:55 PM Kenneth Knowles wrote:
>
>> Noting
I really like the idea of multi-select and automatic "awaiting triage".
Kenn, I think the list you have looks good to me.
On Tue, Dec 6, 2022 at 1:55 PM Kenneth Knowles wrote:
> Noting that what you've listed are the options in the issue template,
> which are then expanded to multiple labels.
Noting that what you've listed are the options in the issue template, which
are then expanded to multiple labels. So focusing on the issue template, I
like the general idea, but maybe we can simplify it even more:
When a user is filing a bug, I think a good outcome is for it to get into
the right
*(To those who identify on the Beam learning path, I supplemented the
original email with additional references/definitions that could help
understand this reply.)*
Hello Robert,
Thank you for reading the document and taking your time to review. The
numbered answers below correspond to the
> Is it possible to not have a default option?
Sadly, no AFAIK. I agree this would help. We could try things like making
the default " " and auto-closing issues that don't pick something other
than the default, that's a pretty rough experience though and not worth it
IMO.
> I definitely think
As someone still newer to Beam, I can attest that the number of labels can
be overwhelming.
Is it possible to not have a default option? Even just getting people to
interact with the dropdown might go a long way, especially if the labels
were fewer and clearer.
Bjorn
On Mon, Dec 5, 2022 at 6:46
Now that we've managed to triage all our incoming issues, perhaps the next
easiest step is to get updates on the *assigned* P1s. After all, in theory
people are working on these and they are quite urgent. If you are assigned
a P1 and not working on it, go ahead and unassign it so we have an
This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/24537 [Bug]: python
