6:59 p.m.
I took another run at closing github issues. As the backlog is tracking
newer and newer, I would encourage anyone who has worked an issue to check
if it maybe has been resolved. If a patch has been merged upstream I think
we can consider the issue resolved unless a backport seems necessary, and if
so, and the backport has not been done, indicate so in the issue (and then
let's get the issue up on the Kanban project board so we can more easily
track it.)
Frank
7:04 p.m.
Ok, I got us down to 62 issues. I have labeled every issue and every issue
has been looked at today.
Some of these are issues under active examination. We should assign owners
to these and get any that are labeled as bugs onto the Ganesha 4 project
board.
Some of these are marked for "analysis", please take a look at these and see
if we can move any along.
Some of these are marked for "verification", please verify these and either
label them as a bug, or close.
We need to look over the enhancements and evaluate if any are things we want
to work on soon, otherwise, we should add them to a new project I just
created "Deep Backlog".
Look over any others and see if we can move them along.
I'd like to see all the active issues that we are working assigned to one or
more people, and added to the Ganesha 4 project board as in progress or
later.
We need to manage our issue backlog better, let's see if we can make it more
manageable.
I plan to look over these more tomorrow and push some around to help get
this manageable.
Also, as we move forward, any issues opened that really don't look like
bugs, but rather are usage questions, let's encourage those discussions to
move to either the devel or support mailing lists so we don't have to have
them occupying "space" in our issue tracker.
Thanks
Frank
From: Frank Filz [mailto:ffilzlnx@mindspring.com]
Sent: Tuesday, July 14, 2020 5:00 PM
To: devel(a)lists.nfs-ganesha.org
Subject: [NFS-Ganesha-Devel] Down to less than 100 open github issues!
I took another run at closing github issues. As the backlog is tracking
newer and newer, I would encourage anyone who has worked an issue to check
if it maybe has been resolved. If a patch has been merged upstream I think
we can consider the issue resolved unless a backport seems necessary, and if
so, and the backport has not been done, indicate so in the issue (and then
let's get the issue up on the Kanban project board so we can more easily
track it.)
Frank
7:48 a.m.
On 7/15/20 8:04 PM, Frank Filz wrote:
Ok, I got us down to 62 issues. I have labeled every issue and every
issue has been looked at today.
Some of these are issues under active examination. We should assign
owners to these and get any that are labeled as bugs onto the Ganesha 4
project board.
Some of these are marked for “analysis�, please take a look at these and
see if we can move any along.
Some of these are marked for “verification�, please verify these and
either label them as a bug, or close.
We need to look over the enhancements and evaluate if any are things we
want to work on soon, otherwise, we should add them to a new project I
just created “Deep Backlog�.
Look over any others and see if we can move them along.
I’d like to see all the active issues that we are working assigned to
one or more people, and added to the Ganesha 4 project board as in
progress or later.
We need to manage our issue backlog better, let’s see if we can make it
more manageable.
I plan to look over these more tomorrow and push some around to help get
this manageable.
Also, as we move forward, any issues opened that really don’t look like
bugs, but rather are usage questions, let’s encourage those discussions
to move to either the devel or support mailing lists so we don’t have to
have them occupying “space� in our issue tracker.
Or maybe have a label for questions, so that we can exclude it from
searches? We've entered an era where many people are less comfortable
with email than with web forums, so having some web-ish way of asking
questions might be nice...
Daniel
9:50 a.m.
On 7/15/20 8:04 PM, Frank Filz wrote:
> Ok, I got us down to 62 issues. I have labeled every issue and every
> issue has been looked at today.
>
> Some of these are issues under active examination. We should assign
> owners to these and get any that are labeled as bugs onto the Ganesha
> 4 project board.
>
> Some of these are marked for “analysisâ€, please take a look at
> these and see if we can move any along.
>
> Some of these are marked for “verificationâ€, please verify these
> and either label them as a bug, or close.
>
> We need to look over the enhancements and evaluate if any are things
> we want to work on soon, otherwise, we should add them to a new
> project I just created “Deep Backlogâ€.
>
> Look over any others and see if we can move them along.
>
>
> I’d like to see all the active issues that we are working assigned
> to one or more people, and added to the Ganesha 4 project board as in
> progress or later.
>
> We need to manage our issue backlog better, let’s see if we can make
> it more manageable.
>
> I plan to look over these more tomorrow and push some around to help
> get this manageable.
>
> Also, as we move forward, any issues opened that really don’t look
> like bugs, but rather are usage questions, let’s encourage those
> discussions to move to either the devel or support mailing lists so we
> don’t have to have them occupying “space†in our issue tracker.
>
Or maybe have a label for questions, so that we can exclude it from searches?
We've entered an era where many people are less comfortable with email than
with web forums, so having some web-ish way of asking questions might be
nice...
There is a label for questions already. So we could use this as a filter for example:
is:issue is:open sort:updated-asc -label:question
Frank
1653
days inactive
1655
days old
3 comments
2 participants
participants (2)
-
Daniel Gryniewicz -
Frank Filz