ext Graham Cobb writes:
> Reporting all bugs found is great. But only "dangerous" issues should
> cause blockages.
My gut feeling is that a specific bug report should always be required
to block a package from entering Extras.
I.e, the logic would be "A package can pass into Extras when there
Graham wrote:
> On Wed, Nov 04, 2009 at 05:36:26PM +, Andrew Flegg wrote:
> >
> > * QA is good.
> > * The criteria are a good start, but need tweaks (see thread)
> > * The packages UI needs some streamlining for testers.
> > * As a tester, a better reminder of the checklist
On Wed, Nov 04, 2009 at 05:36:26PM +, Andrew Flegg wrote:
> I won't be able to make this as I will be onsite at a client, however
> my views can be summarised as:
>
>* QA is good.
>* The criteria are a good start, but need tweaks (see thread)
>* The packages UI needs some streamlin
On Nov 4, 2009, at 18:36, Andrew Flegg wrote:
> On Wed, Nov 4, 2009 at 14:47, Jeremiah Foster
> wrote:
>>
>> There are a number of things to discuss, both technical and
>> non-technical, and it would be great if we could come together and
>> create a list of actionable items so we can make the Q
On Wed, Nov 4, 2009 at 14:47, Jeremiah Foster
wrote:
>
> There are a number of things to discuss, both technical and
> non-technical, and it would be great if we could come together and
> create a list of actionable items so we can make the QA process as
> efficient and usable as possible.
Agreed
Hello,
During the most recent Maemo.org Sprint meeting, Valerio suggested we
get together on IRC and discuss the Quality Assurance process, and
Extras-testing. There are a number of things to discuss, both
technical and non-technical, and it would be great if we could come
together
