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@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