![]() |
Re: extras-testing: many applications to be tested
Those who are members in some forum knows that, but it is not for everyone
|
Re: extras-testing: many applications to be tested
I have voted for everything I use off those lists. It was only about 4 or 5 apps...
|
Re: extras-testing: many applications to be tested
Quote:
|
Re: extras-testing: many applications to be tested
Also that there's, at best, difficult/hazy visibility into what's going on in the repos.
Hardly anyone could tell where to go to give feedback. Is there even a way to see activity going on? It's hard to motivate people when it's all shoved into a corner somewhere without any central means of coordination... |
Re: extras-testing: many applications to be tested
@JohnLF: Thanks!
@Ken-Young: 10 votes would not be so many (3 if they are gived by supertesters), but the community is non well informed and perhaps maybe someone is lazy. I asked the council to improve the process (more supertester, test maratons or some else), but I made a waterhole... @shadowjk: I agree with many of your statements. |
Re: extras-testing: many applications to be tested
Hi, from some time only 6 rates are needed, but there still are a lot of applications to be tested
|
Re: extras-testing: many applications to be tested
Today I counted 240 applications in extras-testing repository.
|
Re: extras-testing: many applications to be tested
How do we look at an inventory list of the extras-testing repository?
|
Re: extras-testing: many applications to be tested
Quote:
|
Re: extras-testing: many applications to be tested
It looks like there are 2 types of issues that are confining them to testing:
1. applications lacking testing reports 2. applications with problems prohibiting them from being promoted, reported to the developer, but with no response or action from the developer (some up to a year) Could there be a way to separate the first type from the second? Then the apps in testing that require developer action could be re-directed from the community back to the developer, and the community could see what needs the focus of testing. Some apps that require developer action in one way of looking at it shouldn't even be in testing any more, because they can't be tested until development issues are resolved. An example is FM Carkit: http://maemo.org/packages/package_in...fm-carkit/0.4/ |
All times are GMT. The time now is 14:39. |
vBulletin® Version 3.8.8