This list also captures the BZs which are in NEW state. The search
description goes like this:
- *Status:* NEW
- *Product:* GlusterFS
- *Changed:* (is greater than or equal to) -4w
- *Creation date:* (changed after) -4w
- *Keywords:* (does not contain the string) Triaged
On Sun,
On Fri, Apr 26, 2019 at 10:55 PM Junsong Li wrote:
> Hello list,
>
>
>
> I have a couple of questions on index translator implementation.
>
>- Why does gluster need callstub and a different worker queue (and
>thread) to process those call stubs? Is it just to lower the priority of
>
[...truncated 6 lines...]
https://bugzilla.redhat.com/1699023 / core: Brick is not able to detach
successfully in brick_mux environment
https://bugzilla.redhat.com/1702316 / core: Cannot upgrade 5.x volume to 6.1
because of unused 'crypt' and 'bd' xlators
https://bugzilla.redhat.com/1695416 /
While I understand this report captured bugs filed since last 1 week and do
not have ‘Triaged’ keyword, does it make better sense to exclude bugs which
aren’t in NEW state?
I believe the intention of this report is to check what all bugs haven’t
been looked at by maintainers/developers yet. BZs
