Request For Candidates: Application Review Board
macoafi at gmail.com
Fri Aug 13 22:30:01 BST 2010
On Fri, Aug 13, 2010 at 4:34 PM, Scott Kitterman <ubuntu at kitterman.com> wrote:
> On Friday, August 13, 2010 02:53:19 pm Rick Spencer wrote:
>> You can use this process to deliver it to the *current release* that you
>> developed it for, you don't have to wait 6+ months for the next release
>> to roll around, and you don't have to master the skills for packaging
>> and delivering into universe.
> That's nonsense. With backports you can have stuff in the development release
> and in backports on the same day.
> I will ask again, what packaging requirements for the archive don't apply to
> this initiative? If we are imposing unnecessary requirements on packages we
> should just remove them in general. If we aren't changing the packaging
> requirements then there's no difference in the barrier to entry associated with
I see one difference in barrier to entry. To get it into a
development release, the author is going to (at some point) have to be
running our development release with toolchains and dependencies
changing under their feet every day and bugs galore. Developing for a
stable release takes less headache and involves less "oh gosh but what
if it doesn't work tomorrow??"
It's not a packaging barrier to entry, but it is a developmental one.
More information about the ubuntu-devel