[GitHub] [incubator-nuttx-apps] btashton commented on issue #14: .asf.yaml: Enable Issues in the apps/ repository.

2020-01-14 Thread GitBox
btashton commented on issue #14: .asf.yaml:  Enable Issues in the apps/ 
repository.
URL: 
https://github.com/apache/incubator-nuttx-apps/pull/14#issuecomment-574402802
 
 
   I would have liked to just have a single issue tracker and just attach 
labels for OS/arm OS/net Website etc... But looks like we are not doing that. 
What about the project feature can we at least have one of those? I cannot 
imagine being able to use that effectively in 5 different places. You can link 
issues from different repos to a single project board. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [incubator-nuttx-apps] btashton commented on issue #14: .asf.yaml: Enable Issues in the apps/ repository.

2020-01-14 Thread GitBox
btashton commented on issue #14: .asf.yaml:  Enable Issues in the apps/ 
repository.
URL: 
https://github.com/apache/incubator-nuttx-apps/pull/14#issuecomment-574396362
 
 
   Do we really want two issue trackers? Splitting the project management board 
across two repos seems even more of an issue. What about the testing repo will 
it also have an issue tracker? I would be much more in favor of having a notice 
in the description that they should file issues against the os project. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services