That's awesome. I must have looked in the wrong place checking on the
status. And I certainly don't want to increase the bureaucratic load on
anyone.

Just that in helping some people in internal review process, I've been
giving advice not to filter too much. We'd rather get problems noticed and
eventually fixed, than have someone say, "I noticed that paragraph made no
sense, " before we try to revise it to accommodate something else.

On Wed, Sep 7, 2022, 12:51 Jeff Garland <jeff_at_[hidden]>
wrote:

>
>
> On Sep 7, 2022, at 6:00 AM, Steve Downey via Lib <lib_at_[hidden]>
> wrote:
>
> An NB comment to fix an issue isn't something to worry about. It's not as
> if they're a score. It's a list of things someone things someone thinks
> that should be dealt with before release.
>
>
> Not worried about it — just trying to save people time on an issue we’re
> going to just resolve anyway.
>
>
> Apply all P0 issues is probably going to be there, too.
>
> If we think this is P0, we should probably make that official.
>
>
> From the link Tim sent, it’s already done — this will get moved at Kona
> pleanary.
>
> *[2022-08-23; Reflector poll]*
>
> Set status to Tentatively Ready after 12 votes in favour during reflector
> poll.
>