|
|
2010-03-04
, 22:55
|
|
|
Posts: 3,203 |
Thanked: 1,391 times |
Joined on Nov 2009
@ Worthing, England
|
#42
|
Greg, could you please search and quote here the first item in QA checklist? hint: link to it can be found at least at http://wiki.maemo.org/Help_testing_software.
and if you don't bother, I can give a spoiler: first item is called something like "bugtracker"
...and if you think that the bugtracker requirements are unfair, drive a change to QA checklist, don't nag at the people who obey the checklist.
http://wiki.maemo.org/Extras-testing...rting_database
Lack of bug reporting database
http://bugs.maemo.org/ is the preferred option. Otherwise it needs to be identified in the http://maemo.org/packages/ page.
|
|
2010-03-04
, 23:01
|
|
|
Posts: 2,121 |
Thanked: 1,540 times |
Joined on Mar 2008
@ Oxford, UK
|
#43
|
| The Following User Says Thank You to pelago For This Useful Post: | ||
|
|
2010-03-04
, 23:05
|
|
|
Posts: 3,203 |
Thanked: 1,391 times |
Joined on Nov 2009
@ Worthing, England
|
#44
|
|
|
2010-03-08
, 00:08
|
|
Posts: 162 |
Thanked: 351 times |
Joined on Apr 2006
@ Cotswolds, UK
|
#45
|
but of a specific type ie, gitorius / bugtracker specific types? - doesn't say that though?
|
|
2010-03-08
, 15:25
|
|
|
Posts: 3,203 |
Thanked: 1,391 times |
Joined on Nov 2009
@ Worthing, England
|
#46
|


| The Following User Says Thank You to noobmonkey For This Useful Post: | ||
|
|
2010-03-08
, 15:44
|
|
|
Posts: 1,070 |
Thanked: 1,604 times |
Joined on Sep 2008
@ Helsinki
|
#47
|
so the only requirement i failed on was the fact that the compiler created the bug tracking link incorrectly....
During which time i registered for a bugtracker account
So allthough my problem is resolved, kinda annoyed... first foray into programming for the N900... and the feeback was essentially not related to my app, but rather something that i couldn't personally control
. If you choose bad materials for your house and the walls crack after a while who is the responsible ? 
| The Following 3 Users Say Thank You to VDVsx For This Useful Post: | ||
|
|
2010-03-08
, 15:45
|
|
|
Posts: 1,070 |
Thanked: 1,604 times |
Joined on Sep 2008
@ Helsinki
|
#48
|
|
|
2010-03-08
, 16:01
|
|
|
Posts: 3,203 |
Thanked: 1,391 times |
Joined on Nov 2009
@ Worthing, England
|
#49
|
Yes, you can control, dpkg-buildpackage will not create bad packages for sure, if you have everything right, the developer is responsible for the quality of is code as for the tools that uses. If you choose bad materials for your house and the walls crack after a while who is the responsible ?
Anyway we're here to help any doubts/concerns, shot
- i agree
- and i do like khertan's package. once i did it once, it makes quick builds easy
|
|
2010-03-09
, 05:33
|
|
|
Posts: 3,159 |
Thanked: 2,023 times |
Joined on Feb 2008
@ Finland
|
#50
|
Let's not get confused on this point. Mikko's app seems to me to meet this criterion.
Now this requirement was added there without any discussion:
A link to the package in the testing queue http://maemo.org/packages/package_in...ng_free_armel/[packagename] The reason is that there will be no bug history once there is published a new version.
it should have been added to proposals
How is "bug history" handled when mailto links are used? Why it's so important to you? For simple packages (such as simple ports) mailto links and package interface are perfectly fine.
And generally testing requirements shouldn't be discussed in small circles like testingsquad-list