In the test day instructions, mention that there is an IoT component in Bugzilla which can be used for reporting problems which don't clearly fall under a specific component (systemd, kernel, etc). Also mention that it's good to mark reported bugs as Blocks: IoT (regardless of the component they are filed under), so that the IoT team have an overview of reported issues. See the IoT tracker bug.

@coremodule @pwhalen any specific dates you guys have in mind?
we have i18n running from 10th-15th. I wouldn't want to put anything there. Can you folks freeze a date? :)

So, the IoT test day is running today:
https://fedoraproject.org/wiki/Test_Day:2020-03-04_Fedora_32_IoT_Edition
but those instructions I posted above are not clearly explained on the wiki.

We will be running another instance of this test day,hence wont close this ticket

The re-run of this Test Day will be on 2020-04-08. thanks @coremodule for helping us fix the dates. This issue will be updated with the new test day pages soon

@coremodule @pwhalen the new test day page is https://fedoraproject.org/wiki/Test_Day:2020-04-08_Fedora_32_IoT_Edition
can you guys give me the test cases or tell me what else needs writing for us to successfully execute the test day?

So, there has been some communication error yesterday, and I just learned from pwhalen that the test day is actually not happening today. I deleted the fedocal event, so that it doesn't confuse people (note that that change might last even 24 hours to propagate to google calendar, which is unfortunate). I didn't find any test-announce announcement, so we should be fine about that.

Next time, somebody please update this ticket, so that everybody watching is informed. And make sure the existing announcements/events are canceled. Thanks.

wiki : https://fedoraproject.org/wiki/Test_Day:2020-04-15_Fedora_32_IoT_Edition

@sumantrom This happened and the results seem to have been transferred, so I guess we can close this ticket?

sure sure closing it!