New Process Review: Post App Release Process

[Matt Zimmerman]

On Tue, Jul 20, 2010 at 01:19:44PM -0700, Kees Cook wrote:
> So, my remaining concerns are the "why would anyone ever put software in the
> main archive if they can get into this repository?"

1. To have the opportunity to be bundled as a default application
2. To provide assurance of updates to users
3. To receive an official endorsement from the Ubuntu project
4. To get top billing in Software Center?
5. To have their application available to users on day 1 of the release? [0]
6. To enable other applications to depend on it

[0] I'm not sure if this has already been discussed, but I think we should
consider starting with a clean slate (empty repository) each release for
this particular repository

> and "everyone will just bundle all their dependencies into their
> applications making security and bloat nasty."

So long as the developer and end user both know what they are getting into,
maybe this is OK to a certain extent.

> As an example that kind of touches both areas, why would Chromium ever want
> to be in the main Ubuntu archive when they could go into this repository?
> They bundle all their libraries and expect to do frequent version bumps.
> (And if they should NOT be in the main archive, what is the benefit of
> being in the main archive in the first place?)

#1, #3, #5 and #6 above.

-- 
 - mdz