Sachin,
That is correct. If you miss a feature freeze date, your feature will be bumped to the next release window. Pat From: Agrawal, Sachin Sent: Thursday, May 14, 2015 7:30 PM To: Lankswert, Patrick; iotivity-dev at lists.iotivity.org Subject: RE: Last call for contributions for 0.9.1 Hi Pat, Can you clarify this statement? ?Failing to do so will result in your contribution being held until the next release? My assumption is that ?master? will still be open for code check-ins, except that the check-in?s after May 28th will NOT be tagged for 0.9.1 release. Is that right? Thanks Sachin 503-264-8071 From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Lankswert, Patrick Sent: Wednesday, May 13, 2015 2:21 PM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Last call for contributions for 0.9.1 To all, The following dates are important for the 0.9.1 release: June 5th ? Code Freeze May 28th ? Feature Complete and Review Complete It is important that contributions be completed by May 28th, so that system testing may start. If you have a contribution that you want considered for 0.9.1 that is not already in gerrit review, you must announce on this list with an estimated date for your submission. Failing to do so will result in your contribution being held until the next release. We are working on a more formal release schedule process what will be published on the wiki. Pat Patrick Lankswert Discovery and Connectivity (Core Stack) Maintainer -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150519/968d7761/attachment.html>
