Has any decision been made wrt bug tracking?
Brennan brought up Jira but many people complained about that and
preferred git issues, I think because of inertia, not based on any
logical reasons. We all love the tools that we know how to use.
But I don't think that any project wide decision has been made.
In the old bitbucket repositories, some people reported issues on the
GIT repositories, but those were mostly just ignored. There was no
process for dealing with the issues in place so most just lingered
around for months or years before someone (me) finally got sick of
seeing them and deleting them.
So I think that just saying the Github issues is the solution is just
sweeping things under the rug. I fully expect that github issues will
be ignore just like bitbucket issues were.
We need something more integrated with day-to-day project management to
assure that someone is handling issues. Jira is a project management
tool, but no one is a Jira expert.
The primary place that I keep issue is in the TODO list file in the
nuttx/ top-level directory. That used to be a simple way for me to keep
track of issues and has travel from CVS on SourceForge, to GIT on
sourceforge, to Bitbucket (all issues were lost on each transition). It
was simple because I could just edit a .txt file and commit it.
But now the TODO list is not simple, it is not friendly, and it is not
open. I can not longer modify the TODO list without submitting a
pull-request. That is not worth the trouble (and I do have some issue
updates that I want to make). We need a user-friendly, open,
management, project-level, single-point bug tracking system ASAP.
Just saying Github issue is not a project level solution. It is just
saying sweep the problems under the rug.
Greg
