ossipena | # 11 | 2010-03-03, 11:00 | Report

I am talking about the process itself. Every package that has broken bugtracker have numerous thumbs up even it should be the first criteria to be correct before further testing and completing the whole QA checklist.

ossipena | # 12 | 2010-03-03, 11:05 | Report

It is more the fact that redirection to another package page isn't very user-friendly and can be really confusing. And i am strongly thinking that anything besides the items in the list should be wrong. Just because there are numerous options available and there are many of those that are easy or really easy to do (tmo/mailto: )

---

Last edited by ossipena; 2010-03-03 at 11:10.

Khertan | # 13 | 2010-03-03, 11:06 | Report

Yeah but maybe everyone do not agree this QA checklist ... !

mikkov | # 14 | 2010-03-03, 11:06 | Report

I have proposed a solution to the problem that 50% of the packages are turned down because of broken bugtracker link in the end of http://wiki.maemo.org/Bugtracker

ossipena | # 15 | 2010-03-03, 11:08 | Report

that is something that must be brought to councils attention. I can't make the decision either no other guys from testing squad.

ossipena | # 16 | 2010-03-03, 11:09 | Report

so you deliberately don't follow the checklist that is a requirement for application to get to extras? what's the point of QA then?

chemist | # 17 | 2010-03-03, 12:20 | Report

Requirement doesnt mean that you can leave it because you think it is stupid!
The QA checklist is there to provide a standard for extras as we expect maemo users not to be linux geeks! I for one would force more than just the things on the list... and change things in procedure. pushing from testing to extras would never be automagical. extras packages would need a bugs.maemo entry a changelog a proper description and last but not least a usability test. (yes I am crazy, but I do QM and QA for a living and have to be like that)

mikkov | # 18 | 2010-03-03, 12:34 | Report

Promotion isn't automatic.

I would prefer automatic bugs.maemo.org entry too. Most of the packages have proper change log, it just isn't displayed anywhere until now. And yes you are crazy

krk969 | # 19 | 2010-03-03, 12:36 | Report

Firstly , I want to make it clear, Im not against testing or QA , I understand the importance of this quite as much as anyone spending more time with S/W than with human beings.

Having said that, I believe its much "easier"(for the lack of a better word ATM) to doctrine the QA process and perform testing of the app than actually develop and maintain one, just considering the fact that is all being done for free (QA included) !
Im not against having a stricter procedure for paid apps however ( I know I'll be blasted for this )
Many little comments that our dear QA leave and give thumbs down too will no doubt "better" the apps, but thats also delaying many good apps and letting down developers somewhere down the line ( be honest here )

Im all for making this the best platform ever for mobile devices, and I seriously think we need better apps than an amazon widget or a weather guide in our portfolio and quick, not next year !
Encouraging paid apps is the other half, which is being discussed elsewhere, the problems with the infrastructure, ovi support etc etc.

All Im saying is we need to reconsider , be a little lenient towards free apps, and they are flagged down for only serious issues, and not for using wrong widgets or colors or buttons being out of place or bugtracker links missing**.
You want everybody to follow rules in a free world is going to be a bit challenging.
Apple/Android may have rules but there the dev know they get rewarded for following rules.

Again, I didnt want to change this into a QA vs DEV war or even say that QA is not needed and we need to pass all apps into extras, just saying we need to be a little more cautious in firing dev who do the software purely in the interest of the platform development or for their karma in life

---

Last edited by krk969; 2010-03-03 at 14:39.

attila77 | # 20 | 2010-03-03, 13:07 | Report

Hey, I thought I'm t-squad ? Anyway, the point is that people who do community QA are not robots nor (mostly ) certified QA engineers. If everybody did everything, there would be no need for TEN thumbs-ups and ten days of quarantine, it would enough for one dude to go through the checklist. The quarantine and redundancy of votes is there exactly to find what others might have missed and to account for differences in device setups, installed apps, etc. So I ask the folks with strong engineering bloodlines to be a bit more pragmatic - it's not a "HA-HA, you forgot/misunderstood it" game. We had some suggestions on the testingsquad list to be more efficiend with the bugtracker link (thumbing down and re-quarantining just because of that is just plain overkill), but still no conclusion there.