Normally I am a fan of keeping things simple and using the simple github issue tracker, but we have a few issues that I think make that less practical.
1) Multiple repos. We might have an issue or feature the spans the os, app, and website repos now we need to file tickets in each or something equally ugly 2) Sounds like we have people who cannot use Github, now they cannot use the issue tracker so we have people using the mailing list which is less ideal. 3) We already have JIRA linked with the projects. To see how this is already setup I tested it by doing this: 1) Created a dummy issue in JIRA https://issues.apache.org/jira/browse/NUTTX-1 2) Create a PR that mentioned this issue NUTTX-1 https://github.com/apache/incubator-nuttx/pull/15 3) The issue was automatically linked with the PR as you can see in the issue. There is even more context if you click All under Activity. Looks like the bot did not write back to the github PR which is unfortunate, but not that bad. --Brennan On Sun, Dec 29, 2019 at 12:13 PM Gregory Nutt <spudan...@gmail.com> wrote: > It has been reported to me that Issues are disabled at > https://github.com/apache/incubator-nuttx-apps: > <https://github.com/apache/incubator-nuttx-apps> > > https://bitbucket.org/nuttx/apps/issues/15/null-dereference-in-ftp-size-command > > We need to decide how people report problems to us. GIT issues? Jira? > d...@apache.org? We need to make some decisions. I think Jira would > give us the best bug tracking options. GIT issues is well integrated on > github. I think d...@apache.org is a bad idea. > > There is a backlog of Issues/bugs at > https://bitbucket.org/nuttx/nuttx/issues?status=new&status=open and > https://bitbucket.org/nuttx/apps/issues?status=new&status=open (and also > issues in the top-level NuttX TODO file). I have a personal list of > things that I thing should be done as well. > > We probably need another Confluence page talking about bug-reporting. > > Greg > > >
