On 01/22/2014 02:11 PM, Pat McGowan wrote: > On 01/22/2014 12:48 PM, Jamie Strandboge wrote: >> * when adding a framework, we need to understand what a microversion means if >> we are going to use it. Ie, in terms of apparmor policy, is there a >> difference between ubuntu-14.04-qml and ubuntu-14.04.1-qml such that >> "ubuntu-14.04-qml, ubuntu-14.04.1-qml" is supposed to be supported in the >> click manifest? > Yes, we had discussed the idea of a minor version which adds APIs to a > base framework revision. But I think we could stipulate a single > apparmor policy for these.
Cool, agreed. >> * click-review-tools needs to be adjusted to enforce the outcomes of this >> thread >> >> With the above, an app developer then has a choice of either uploading >> differently versioned apps with different framework bases to the the store or >> declaring the earliest (supported) framework desired for the app. >> >> As an aside, I'd like to see the outcomes of this codified somewhere so that >> the >> SDK, foundations/phonedations, security, community and app store teams are >> all >> on the same page and to ensure adding a new framework works correctly. > I started a document to record this and will share. > Awesome, thanks! Is this ready for a wider audience yet? Alexander suggested in a later message to the thread some rules for defining frameworks that can be added (and once its codified, I can adjust click-apparmor and the review tools). -- Jamie Strandboge http://www.ubuntu.com/ -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
