Request For Candidates: Application Review Board
rick.spencer at canonical.com
Fri Aug 13 20:39:49 BST 2010
On Fri, 2010-08-13 at 15:23 -0400, Andrew SB wrote:
> I applaud the effort to make contributing to Ubuntu easier for all
> different kinds of people, but I still haven't heard an answer to one
> of Scott's earlier questions that has nagged me as well.
> Who is responsible for pushing these new apps to the development
> release? As Scott said, "Once the next release hits they won't be in
> the current release anymore because we skipped the part where we get
> the packages into the development release." Are we creating a
> permanent split in the archive with two completely different
This process does represent a significant change in the way users
related to application in Ubuntu.
I don't think anyone is specifically responsible for ensuring that
applications go into the current development release.. Maverick will be
the first release where we are using this process, so we will learn a
lot and tweak the process as needed to improve it. For example, if a
path that includes both the stable release and the development release
is deemed required, we can add such as a path.
It's not necessarily granted that an application written for a stable
release is relevant for future releases. For example, an application
"Super Bowl 2010" may only be relevant for the 10.10 release. Or perhaps
the application provides functionality which is built into another core
app in the development version, etc...
On the whole, I'm hoping that many application authors find their
experience releasing an application to be enjoyable and a stepping stone
to more in depth contributions to Ubuntu of FLOSS, though. For instance,
by moving their application into Debian, and having it end up in Debian,
Ubuntu, and other distros that way.
More information about the ubuntu-devel