Regarding the Java/Android unit tests for Security 2.0 (ASACORE-3383) we have come to a conclusion for the initial 16.10 release.
Per discussion with Kevin Kane, George Tang, Marcello and myself with a few others we decided on the following actions: - Don’t block the 16.10 release on this unit test code. - Complete the unit test code for 17.04 as soon as possible, and commit it to the master branch. These don’t need to be on RB16.10 unless they reveal problems. - If the unit tests reveal blocking gaps or bugs, then we should discuss a 16.10a release, and backporting the unit tests to RB16.10. For the 16.10 release we will not be providing JUnit tests on Android for Security 2.0. If we discover any issues while writing the unit tests (which should be complete within the next two weeks) we will quickly do a 16.10a patch release. The reasoning behind this is that the Door Sample is sufficient for testing Security 2.0 interoperability. However, the ability to write a Security Manager in Java/Android would be tested by these JUnit tests, and it is therefore currently unknown if this is possible/functional. Thanks, Josh Josh Spain Director of Engineering Affinegy, Inc. t.512-535-1700 x1006 a. 1705 S Capital of Texas Hwy, Suite 310, Austin, TX 78746 USA Website <http://affinegy.com> Email <[email protected]> <http://www.linkedin.com/in/joshspain> <http://twitter.com/affinegy> Latest Tweet: <https://twitter.com/Affinegy> RT @rcrwirelessnews: <https://twitter.com/rcrwirelessnews:> Chat on #IoT <https://twitter.com/IoT> interoperability w/ @affinegyart, <https://twitter.com/affinegyart,> CTO of @Affinegy, <https://twitter.com/Affinegy,> and merger of @AllseenAlliance <https://twitter.com/AllseenAlliance> & @OpenConnOrg <https://twitter.com/OpenConnOrg> https:/… Read More <https://twitter.com/Affinegy/statuses/792597185183395841> <https://twitter.com/Affinegy>
_______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
