Junmo,

Thiago is right. I am working on an estimate for Spec A compliance right now. I 
cannot say what it will do to the schedule until I am done. However, you should 
be cautious on the dates as they may not be grounded on the actual state, 
progress and the work remaining.

Pat

> -----Original Message-----
> From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-
> bounces at lists.iotivity.org] On Behalf Of Thiago Macieira
> Sent: Tuesday, April 14, 2015 10:18 AM
> To: iotivity-dev at lists.iotivity.org
> Subject: Re: [dev] Schedule for IoTivity v0.9.1 Release
> 
> On Tuesday 14 April 2015 19:03:34 ??? wrote:
> > Hi Bernie,
> >
> > Junmo?s schedule is not new one. The schedule below & in the attached
> > mail was shared on 3/24 and discussion has been on-going.
> 
> Hi June
> 
> That schedule rested on CA being merged at no later than March 30, but like
> you said that was delayed by almost 2 weeks. Are you saying that Junmo's
> email is the update to the schedule?
> 
> I don't see how. If we're two weeks late, shouldn't the release date have
> been pushed by two weeks compared to the original plan?
> 
> We're reacting to the surprising manner in which this has come, without
> discussion.
> 
> > And actually April release as Spec vA compliant release was reported
> > to BoD at the OIC OSWG F2F meeting.
> 
> I don't see how that is relevant. Work takes as long as work it takes.
> 
> > IoTivity QA release was supposed to start from 4/6, but it is being
> > delayed by almost 2 weeks.
> 
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
> 
> _______________________________________________
> iotivity-dev mailing list
> iotivity-dev at lists.iotivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7198 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150414/e7f20577/attachment.p7s>

Reply via email to