I can make one if you'd wish, but due to recent comments, I'll need an
official "please change it" message.


On Tue, 2015-07-21 at 20:23 +0000, ??? wrote:
> I am in the biz trip right  now so i cannot see it. But it is supposed
> to be "0.9.2-rc1"  
> It can be changed?
> 
> 
> June
> 
> Sent from Mobiledesk
> 
> 
> ---?? ???---
> ??? : Keane, Erich/erich.keane at intel.com
> ???? : 2015/07/21 08:53 (GMT-07:00)
> ?? : Re: [dev] 0.9.2-dev Branch created, feature FREEZE for Plugfest
> 3
> 
> Ah, I see a "RC1" tag. I believe it is supposed to be 0.9.2-RC1, right
> June?
> 
> 
> On Tue, 2015-07-21 at 10:09 +0900, ???(Uze Choi) wrote:
> > Hi Erich,
> > 
> > According to the release team request, RC1 tag has been created on
> the 0.9.1-dev branch already.
> > 
> > BR, Uze Choi
> > -----Original Message-----
> > From: Keane, Erich [mailto:erich.keane at intel.com] 
> > Sent: Tuesday, July 21, 2015 1:05 AM
> > To: Kesavan, Vijay S
> > Cc: Keany, Bernie; iotivity-dev at lists.iotivity.org;
> uzchoi at samsung.com
> > Subject: Re: [dev] 0.9.2-dev Branch created, feature FREEZE for
> Plugfest 3
> > 
> > Vijay/Uze, thank you very much for completing my very partial list.
> > This release will definitely be quite an impressive list of
> additional features.
> > 
> > I created the -beta tag so that the validation engineers can begin
> testing, though it is obviously up to the release team to decide when
> > RC1 is officially started.
> > 
> > 
> > On Sun, 2015-07-19 at 16:20 +0000, Kesavan, Vijay S wrote:
> > > In addition to the features listed by Erich and Uze, the release
> also 
> > > includes
> > > * Core Spec A compliance
> > > * Security Spec A mandatory feature compliance
> > > 
> > > Detailed release notes will be provided along with the full
> release.
> > > 
> > > --Vijay
> > > 
> > > -----Original Message-----
> > > From: iotivity-dev-bounces at lists.iotivity.org 
> > > [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf
> Of ???(Uze 
> > > Choi)
> > > Sent: Sunday, July 19, 2015 2:35 AM
> > > To: Keany, Bernie; Keane, Erich; iotivity-dev at lists.iotivity.org
> > > Subject: Re: [dev] 0.9.2-dev Branch created, feature FREEZE for 
> > > Plugfest 3
> > > 
> > > Hi All,
> > > 
> > > There are the number of great features in this release.
> > > Furthermore, this new branch should have included new Security and
> Service features also.
> > > 
> > > Service point of view, there are several new feature called as
> Resource Encapsulation Layer (called as Manipulation before) which
> includes Resource Broker, Resource Cache, Resource Builder, Resource
> Container. This new feature and corresponding existing service code
> update will be in the release also.
> > > By today, we will merge it into master and 0.9.2 release branch
> also.
> > > 
> > > Then we like to request to June tagging official RC1 who is
> release function leader. If RC1 should be the after fixing the Android
> server and RI/CA 's bugs, raise the issue ASAP. I think, this will
> affect the official testing start time.
> > > 
> > > BR, Uze Choi
> > > -----Original Message-----
> > > From: iotivity-dev-bounces at lists.iotivity.org
> [mailto:iotivity-dev- 
> > > bounces at lists.iotivity.org] On Behalf Of Keany, Bernie
> > > Sent: Saturday, July 18, 2015 11:14 AM
> > > To: Keane, Erich; iotivity-dev at lists.iotivity.org
> > > Subject: Re: [dev] 0.9.2-dev Branch created, feature FREEZE for 
> > > Plugfest 3
> > > 
> > > This is a pretty impressive set of features that come into the
> codebase on the heels of the recent v0.9.1 release. Thanks to all the
> contributors and the work of the maintainers for achieving this
> goal ..
> > > 
> > > Bernie
> > > 
> > > 
> > > On 7/17/15, 6:04 PM, "Keane, Erich" <erich.keane at intel.com> wrote:
> > > 
> > > >Hi all-
> > > >
> > > >As you know, today is the feature-freeze for the Plugfest 3.
> I've 
> > > >created a branch to contain this version, which will receive 
> > > >bug-fixes as they are discovered. Additionally, the tag
> 0.9.2-beta 
> > > >has been created to be used as a reference for validation.
> > > >
> > > >The major features of this release are: CBOR, Experimental IPv6 
> > > >Support, Experimental Remote-Access Support.
> > > >
> > > >Currently, The Android server is having trouble PUT/POST
> requests.
> > > >Additionally, the LOW QOS observation cancellation does not
> properly 
> > > >work throughout the stack, resulting in the server continuing to
> send 
> > > >out notifications.
> > > >
> > > >For the RI/CA layers, please continue to submit fixes to all bugs
> to 
> > > >master (noting that they apply to the 0.9.2-dev branch), and I
> will 
> > > >cherry-pick them to the branch. If your patch applies ONLY to
> the 
> > > >0.9.2-dev branch you'll be required to explain to Pat why that is
> the 
> > > >case, and we'll discuss it from there.
> > > >
> > > >General feature-development can still be contributed to master, 
> > > >though they will not be included in the Plugfest 3 release.
> > > >
> > > >Validation: Feel free to test the 0.9.2-dev branch or the
> 0.9.2-beta 
> > > >tag, though note that the former will be changing with bug-fixes.
> I 
> > > >anticipate a number of bug fixes and a -rc1 sometime next week.
> > > >
> > > >Thank you all for your contributions, and have a great weekend!
> > > >
> > > >-Erich 
> > > >
> > > >
> > > >_______________________________________________
> > > >iotivity-dev mailing list
> > > >iotivity-dev at lists.iotivity.org
> > > >https://lists.iotivity.org/mailman/listinfo/iotivity-dev
> > > 
> > > _______________________________________________
> > > iotivity-dev mailing list
> > > iotivity-dev at lists.iotivity.org
> > > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
> > > 
> > > _______________________________________________
> > > iotivity-dev mailing list
> > > iotivity-dev at lists.iotivity.org
> > > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
> > 
> > 
> 
> _______________________________________________
> iotivity-dev mailing list
> iotivity-dev at lists.iotivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
> 
> 
> 
> 

Reply via email to