Request For Candidates: Application Review Board

Michael Bienia michael at
Tue Aug 10 09:47:32 BST 2010

On 2010-08-09 17:53:09 -0400, Elliot Murphy wrote:
> However, I believe the new process will be easier to market to
> application developers that we definitely need to be winning over, and
> the flowchart (subjectively, when I imagine explaining this to an app
> developer that I'm trying to win over) feels less clunky than going
> into the dev release and then immediately into backports. It also
> prevents the app developer from needing to run the development release
> of Ubuntu, instead they can stay on a stable foundation and focus
> exclusively on building the app without worrying about the platform
> shifting beneath their feet from day to day. I love running the dev
> version of Ubuntu, but I've seen it stress out upstream app developers
> over and over when they just want to focus on building their app
> without thinking about libraries or desktop changing underneath them.

Some points are not yet clear to me in this process:
- will those packages end in the "main" archive or a seperate one (like
  "partner")? or will they stay in a PPA?
- how do updates of those packages work? which process is to follow?
  this one or SRU or a different one?
- who is responsible for the forward porting of the application to the
  next Ubuntu release? And will this happen while the next Ubuntu
  release is still in development or only once it got released and the
  app developer re-applies to get his app added to this new Ubuntu
  release too?

And do I understand it correctly that applications which need yet
unpackaged libraries are not eligible for this process?


More information about the ubuntu-devel mailing list