NWAM West: 8:30AM MPK/11:30AM BUR/4:30PM DUB Attendees: John, Michael, Victor, Anurag, Karen, Alan, Renee
1. Phase 1 ON development status See the task wiki: http://wikis.sun.com/display/NWAM/P1+Dev+Task+Status Current target is for dev complete on 4/17. 2. Question about nwamadm interact behavior: currently, can't start monitoring events if nwam is not enabled; which means it's not possible to catch events at start-up. Dev team will look at this; this is clearly a desirable feature, but it's not clear how this works given that nwamadm is connecting to nwamd's door server to get events, and nwamd isn't running if nwam is not enabled (so no door server). 3. Need an "ignore this ncu" activation mode. We had this way-back-when (the "don't touch this" activation type, a.k.a. the MC Hammer option), but that notion morphed into the manual activation. Manual activation, though, is not exactly what we want. Manual activation means that the user changes the enabled stated by manually enabling/disabling via the UI; but nwam does have a desired state associated with the NCU, so if nwam is restarted, regardless of what the actual state was prior to the restart, it will enforce the value stored in the enabled property when it starts up. "Don't touch this" means that nwam should never change the state of the NCU. This probably needs to be a post-integration RFE. NWAM East: 6:00PM MPK/9:00AM BJS Attendees: Lizhong, Eric, John, Alex, Victor, Renee 1. The wifi driver team will be reviewing the wifi test assertions. Thanks to Lizhong and Alex for facilitating that! 2. Question about the tests in the common gate: it doesn't appear that we're testing for correct activation of configuration. Is that still to come? Yes, Alex has much of it written, but has not integrated it into the common gate yet. 3. Eric requested that we look at ways to speed up integration of the test suite, so that it happens closer to, if not concurrent with, the feature integration. All kinds of goodness comes with getting the test suite integrated sooner rather than later! So if it's possible to help out with code review, get test code fixes addressed, etc. while we're wrapping up the feature code for integration, please do so. -renee
