On 03/16/2017 02:50 AM, ??? (Uze Choi) wrote: > Hi, Feature contributors in 1.3 release. > > > > Please check as below. and respond by this week. > > > > [Jira Registration/Tagging into wiki] > > Please add Jira tick link on https://wiki.iotivity.org/1.3_release_plan. as > like security related item. > > Introspection, Versioning, Endpoint > > MPM, AllJoyn Bridge, UPnP Bridge > > CoAP Native Cloud Project items. > > Generic Java Binding.
Just to circle back on this once more - should IoTivity wiki entries or Jira tickets contain links to non-public OCF resources? It's clear that certain developers of iotivity may have to refer to unpublished materials in preparing for a new release, and are able to do so if they "live in both camps", but including such links in the public IoTivity resources makes them opaque to readers without OCF member status. If the team feels this is okay, I won't ask about it any more. Examples: This 1.3 wiki page: === Security updates (see dashboard spreadsheet for details) (the "dashboard spreadsheet" is a link to https://workspace.openconnectivity.org/apps/org/workgroup/security_os_tg/download.php/8839/IoTivity%201.3%20Security%20Feature%20Dashboard.xlsx) === Jira ticket to provide software update hooks (https://jira.iotivity.org/browse/IOT-1786): === The CR 24 can be found on Kavi: https://workspace.openconnectivity.org/apps/org/workgroup/security_wg/download.php/8395/CR_SecWG_OCF1.0_00024.004_SoftwareUpdate.docx ... and the OCF bugzilla is private: The Bugzilla issue number is 1384: https://bugzilla.openconnectivity.org/show_bug.cgi?id=1384 ===
