On Monday 13 April 2015 06:24:48 ??? wrote: > Dear IoTivity Dev. Members, > > I'd like to kindly remind the schedlue of Iotivity v0.9.1. > If anyone has any comment or suggestion, please share it. > > 4/15 Release Iotivity Official Q/A Version IoTivity > - Tag Name: 0.9.1-RC1 > - CA merged version > - Need to all Q/A issues > 4/17 Complete merge of Android API > 4/20 IoTivity v0.9.1_RC1 Test Report > 4/21 Release IoTiviy 0.9.1-RC2 version, incldue followings > - Tag Name: 0.9.1-RC2 > - Andorid API > - BT/BLE should be completed > 4/24 Q/A Exit (Need consent between Q/A & Dev) > 4/27 Web Site Open
Hi Junmo Why are we releasing release candidates without the full API that is going to be in the final version? We should first include *everything* that is going to be in the final before we release a release candidate. I'd also be very skeptical about releasing a release candidate before the QA report comes in. If we don't know the quality, we shouldn't call it RC because it's not a candidate. I recommend calling it "beta". -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
