← Back to team overview

ubuntu-appstore-developers team mailing list archive

Re: Summary: Review requirements call

 

Hey,

thanks a lot for your thoughts on this, Dave!

On 02.08.2013 18:27, Dave Morley wrote:
> One thing I would like to see tested at least the first time round
> would be handling of the apps during a phone update.  The last thing
> we want when upgrading the phone images is all the users installed
> apps being removed or still being installed but not visible in the
> apps lens.  With regards phone updates rather than app updates.

I think this is going to be rather hard, especially with new apps coming
in, as they very likely don't have updates yet. :-) Aren't click apps
installed into a versioned directory?


> With regard to app updates I'm assuming that unless the dev is
> changing text, images etc that then can just click edit on the click
> package and upload the new package.

There was only some discussion about apps changing security requirements
during updates. Is there anything else we should consider an important case?


> For the initial manual review process to have a detailed example of
> what to look for/at would be good, or a video/hangout so we can see a
> review in progress.  Monkey see monkey do learning and all that.

We will all have to learn what's important by doing the reviews
ourselves. Maybe a collective review session over hangout would help?


> One last thing would be a prior art check unless we are leaving that
> to the abuse reporting mechanism? I'm assuming it will be easy enough
> to check that an app that is published via click won't allow an app
> with the same name to be submitted.

How much of a concern is this?

Have a great day,
 Daniel

-- 
Get involved in Ubuntu development! developer.ubuntu.com/packaging
Follow @ubuntudev on identi.ca/twitter.com/facebook.com/G+


Follow ups

References