[maemo-developers] QA from extras-devel to extras-testing

[From: Jeremiah Foster]

On May 4, 2009, at 11:11, Dave Neary wrote:

> Hi,
>
> Jeremiah Foster wrote:
>> On May 2, 2009, at 16:11, Glen Ditchfield wrote:
>>> If packages don't have to have bug trackers, then QA will have to
>>> build some
>>> infrastructure to keep track of positive and negative votes, and the
>>> packager's comments on the negative votes, and declarations that the
>>> problems
>>> that caused the negative votes have been fixed  ... maybe it would
>>> be easier
>>> to require that packages have bug trackers, and use them for QA?
>>
>> Who is going to build all of this infrastructure? Won't this type of
>> requirement help create separate private repos?
>
> Isn't this bugs.maemo.org? Is there a good reason not to use this for
> Maemo packaging issues?

I think that is a fine idea. Do people know that it can be used for  
this sort of thing? I personally welcome packaging issues relating to  
maemo to be submitted to bugs.maemo.org and will work hard to keep up  
to date with them.

> For bugs in the software, the individual package's bug tracker is more
> appropriate - I hate to see bugs aggregate in a distribution's bug
> tracking system & never make it upstream to the people who know how to
> fix them.

Good point. But haven't we avoided the issue of requiring "that  
packages have bug trackers, and use them for QA"? How is one going to  
enforce bug trackers on applications submitted to Maemo? And if  
someone does not want to create a bug tracker, for whatever reason,  
how can we convince them not to open their own repo if Maemo rejects  
their package?

Jeremiah