.asf.yaml: Enable Issues in the apps/ repository. #14
Conversation
|
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. |
|
Yes, most definitely. I do NOT want security violations against crappy little applications in apps/ being reported against the OS. The is a disservice to the years of effort that have but put into it. A badly done afternoon's work develop a bad application MUST not reflect on the core OS. We cannot have that. It is very important (at least to me) that we separate the issues base upon what they are reported against. |
|
We will also need to eventually enable issues in incubator-nuttx-testing and incubator-nuttx-website too. |
|
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. |
|
I really, really, really dislike that idea. I do not want apps/ issues in the OS. That is a really repulsive concept to me and I have to resist that idea with all means available to me. I am not opposed to one location. But I am strongly opposed to the one location being the OS. That is an awful idea. I don't want that. I don't want the OS to the be the toxic dumping ground for all issues. I ONLY want OS issues reported against the OS. I fell VERY strongly about that. If you want a single issue tracker we can talk about that, but NOT the OS! Please. |
|
The PPMC as a whole should discuss this and come to some consensus on it. I suggest you start a thread on the mailing list. |
|
There already is a thread. But is never came to a consensus. Some wanted to use Jira, some wanted to use Github issues. I don't really care, but I don't want all issues reported against the OS. That is wrong. Especially after this BS discussion about security in a pre-Apache code release. I do not want those reports associated with the core OS. I am really not comfortable with that at all. That would get a -1 vote from me. |
|
"There already is a thread." There were the threads called "Bug Tracking" started on January 3 and again as "Issue Reporting" sometime before January 9 |
|
I'm aware of those threads. Why is action being taken if consensus hasn't been reached? Consensus sometimes can be hard and takes time, but I don't think there's a huge rush here. How many app issues have been raised to date in the main repo? I'd also suggest the PPMC focus on dealing with security issues as per the documented process. |
|
Let's keep everything as it is now so that no application issues are reported against the OS in the mean time. I am not the right person to deal with the security nonsense. I don't have sufficient patience for that. |
…ter was read
#0 0x43c7443a in strnlen nuttx/libs/libc/string/lib_strnlen.c:42
apache#1 0x43c698aa in vsprintf_internal nuttx/libs/libc/stdio/lib_libvsprintf.c:933
apache#2 0x43c6ca80 in lib_vsprintf nuttx/libs/libc/stdio/lib_libvsprintf.c:1383
apache#3 0x4409c0bd in vsnprintf nuttx/libs/libc/stdio/lib_vsnprintf.c:72
apache#4 0x47137cd0 in vcmocka_print_error apps/testing/cmocka/cmocka/src/cmocka.c:2097
apache#5 0x47139573 in cmocka_print_error apps/testing/cmocka/cmocka/src/cmocka.c:2422
apache#6 0x471376ff in string_equal_display_error apps/testing/cmocka/cmocka/src/cmocka.c:1410
apache#7 0x471379a0 in _assert_string_equal apps/testing/cmocka/cmocka/src/cmocka.c:1952
apache#8 0x4433d972 in read_default apps/testing/drivertest/drivertest_uart.c:242
apache#9 0x4713c6cd in cmocka_run_one_test_or_fixture apps/testing/cmocka/cmocka/src/cmocka.c:3029
apache#10 0x4713d487 in cmocka_run_one_tests apps/testing/cmocka/cmocka/src/cmocka.c:3143
apache#11 0x4713f2ca in _cmocka_run_group_tests apps/testing/cmocka/cmocka/src/cmocka.c:3294
apache#12 0x443444c6 in cmocka_driver_uart_main apps/testing/drivertest/drivertest_uart.c:358
apache#13 0x4409a472 in nxtask_startup nuttx/libs/libc/sched/task_startup.c:72
apache#14 0x43dc92e7 in nxtask_start nuttx/sched/task/task_start.c:116
apache#15 0x43e31f00 in pre_start nuttx/arch/sim/src/sim/sim_initialstate.c:52
Signed-off-by: zhangshoukui <[email protected]>
…ter was read
#0 0x43c7443a in strnlen nuttx/libs/libc/string/lib_strnlen.c:42
#1 0x43c698aa in vsprintf_internal nuttx/libs/libc/stdio/lib_libvsprintf.c:933
#2 0x43c6ca80 in lib_vsprintf nuttx/libs/libc/stdio/lib_libvsprintf.c:1383
#3 0x4409c0bd in vsnprintf nuttx/libs/libc/stdio/lib_vsnprintf.c:72
#4 0x47137cd0 in vcmocka_print_error apps/testing/cmocka/cmocka/src/cmocka.c:2097
#5 0x47139573 in cmocka_print_error apps/testing/cmocka/cmocka/src/cmocka.c:2422
#6 0x471376ff in string_equal_display_error apps/testing/cmocka/cmocka/src/cmocka.c:1410
#7 0x471379a0 in _assert_string_equal apps/testing/cmocka/cmocka/src/cmocka.c:1952
#8 0x4433d972 in read_default apps/testing/drivertest/drivertest_uart.c:242
#9 0x4713c6cd in cmocka_run_one_test_or_fixture apps/testing/cmocka/cmocka/src/cmocka.c:3029
#10 0x4713d487 in cmocka_run_one_tests apps/testing/cmocka/cmocka/src/cmocka.c:3143
#11 0x4713f2ca in _cmocka_run_group_tests apps/testing/cmocka/cmocka/src/cmocka.c:3294
#12 0x443444c6 in cmocka_driver_uart_main apps/testing/drivertest/drivertest_uart.c:358
#13 0x4409a472 in nxtask_startup nuttx/libs/libc/sched/task_startup.c:72
#14 0x43dc92e7 in nxtask_start nuttx/sched/task/task_start.c:116
#15 0x43e31f00 in pre_start nuttx/arch/sim/src/sim/sim_initialstate.c:52
Signed-off-by: zhangshoukui <[email protected]>
No description provided.